Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd8be059158c1b0a23473c188f91f5eb60b49b9aa15d565688c9a850ed867527

Tx prefix hash: 014ba14421947ca33a1bfb771c2e463c5bf373fe1f0d937cbaf93901ae6cf210
Tx public key: a19d268e1f579df683a12e90ef9ef99ea3eba8cbb3188e598db5764ec812d816
Timestamp: 1751382506 Timestamp [UCT]: 2025-07-01 15:08:26 Age [y:d:h:m:s]: 00:140:23:00:07
Block: 1316609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98962 RingCT/type: yes/0
Extra: 01a19d268e1f579df683a12e90ef9ef99ea3eba8cbb3188e598db5764ec812d816021100000004e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6e9d0288eff64efc109a9e48cf36eb6c098458a6fd8ac624ef7221fc7e729ca 0.600000000000 1804270 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": 1316619, "vin": [ { "gen": { "height": 1316609 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6e9d0288eff64efc109a9e48cf36eb6c098458a6fd8ac624ef7221fc7e729ca" } } ], "extra": [ 1, 161, 157, 38, 142, 31, 87, 157, 246, 131, 161, 46, 144, 239, 158, 249, 158, 163, 235, 168, 203, 179, 24, 142, 89, 141, 181, 118, 78, 200, 18, 216, 22, 2, 17, 0, 0, 0, 4, 228, 220, 144, 9, 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