Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b521c70b437547b0b77ab3a75a1caae5035d4bd0a5b1b1877a4cbbbd124db8f

Tx prefix hash: 1e7f8cf7d95cb92dd5466ac5d34ca63d7d758dece9877e8bfac446f58964d09a
Tx public key: 4b6813b658032310c38f39e04426ae4d97b511459f8596c2e9098e35a352384e
Timestamp: 1762491907 Timestamp [UCT]: 2025-11-07 05:05:07 Age [y:d:h:m:s]: 00:063:06:52:50
Block: 1406710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45320 RingCT/type: yes/0
Extra: 014b6813b658032310c38f39e04426ae4d97b511459f8596c2e9098e35a352384e02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6611e32fab0bb7321829a89d15c318836d26c9684419bfcd397032f4f3739b8 0.600000000000 1895099 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": 1406720, "vin": [ { "gen": { "height": 1406710 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6611e32fab0bb7321829a89d15c318836d26c9684419bfcd397032f4f3739b8" } } ], "extra": [ 1, 75, 104, 19, 182, 88, 3, 35, 16, 195, 143, 57, 224, 68, 38, 174, 77, 151, 181, 17, 69, 159, 133, 150, 194, 233, 9, 142, 53, 163, 82, 56, 78, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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