Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: a4924f5b0dc9a4d697c459cf1f67a4a966713ad4a310e800da66ccdd13927a41

Tx prefix hash: 8ac730341bb739447e8b5291bacca09a9d85cfa08d5fcd93d8288482187a0d1d
Tx public key: 7c9c7313bef9c8331790525cf2d2c29acd97b647cff27b2c80afd04c506f3d46
Timestamp: 1722664789 Timestamp [UCT]: 2024-08-03 05:59:49 Age [y:d:h:m:s]: 00:315:04:23:10
Block: 1079650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225130 RingCT/type: yes/0
Extra: 017c9c7313bef9c8331790525cf2d2c29acd97b647cff27b2c80afd04c506f3d4602110000000e91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ca470bf6e925c6afb13cab632c48b4f377adb449de4cd2779f49afadc336e00 0.600000000000 1552699 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1079660, "vin": [ { "gen": { "height": 1079650 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ca470bf6e925c6afb13cab632c48b4f377adb449de4cd2779f49afadc336e00" } } ], "extra": [ 1, 124, 156, 115, 19, 190, 249, 200, 51, 23, 144, 82, 92, 242, 210, 194, 154, 205, 151, 182, 71, 207, 242, 123, 44, 128, 175, 208, 76, 80, 111, 61, 70, 2, 17, 0, 0, 0, 14, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8