Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf4d48244a469d2ebc318e93287f325e780db2cf36f11e368719b90bd33c975d

Tx prefix hash: e852bb3365309fc1c06b4309f7c648330e281a4723358371333a25e5fe2bac3c
Tx public key: 20aa0a706bd81d1e059b4cc0ebb02c47f7a6a4b1a14e5bbfe41cd415a0657701
Timestamp: 1756048118 Timestamp [UCT]: 2025-08-24 15:08:38 Age [y:d:h:m:s]: 00:093:22:13:45
Block: 1353489 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67074 RingCT/type: yes/0
Extra: 0120aa0a706bd81d1e059b4cc0ebb02c47f7a6a4b1a14e5bbfe41cd415a06577010211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 451a4f3d102fdf7de26deaf4f3440987adc7e4ae2480d690dcafc162dca77fc3 0.600000000000 1841464 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": 1353499, "vin": [ { "gen": { "height": 1353489 } } ], "vout": [ { "amount": 600000000, "target": { "key": "451a4f3d102fdf7de26deaf4f3440987adc7e4ae2480d690dcafc162dca77fc3" } } ], "extra": [ 1, 32, 170, 10, 112, 107, 216, 29, 30, 5, 155, 76, 192, 235, 176, 44, 71, 247, 166, 164, 177, 161, 78, 91, 191, 228, 28, 212, 21, 160, 101, 119, 1, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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