Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 616c7a560ec395f21c261cea6a83495679cbfc226f2ef61b7e5ddbc5406b74ce

Tx prefix hash: d1def8c44c4a0e9ff2e940c6511aba25adacc13ca8fa3767e966e19d577508cd
Tx public key: b52eee809c72eaa6370c8df5705e23c10c60d35a59236a47ea0a80b9375cdc22
Timestamp: 1716229954 Timestamp [UCT]: 2024-05-20 18:32:34 Age [y:d:h:m:s]: 00:317:13:53:14
Block: 1026308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226974 RingCT/type: yes/0
Extra: 01b52eee809c72eaa6370c8df5705e23c10c60d35a59236a47ea0a80b9375cdc2202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 060bb8e9d5262245eaad14b9dbb3229f7217942130d0ca89a1ef6decea4e1141 0.600000000000 1493319 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": 1026318, "vin": [ { "gen": { "height": 1026308 } } ], "vout": [ { "amount": 600000000, "target": { "key": "060bb8e9d5262245eaad14b9dbb3229f7217942130d0ca89a1ef6decea4e1141" } } ], "extra": [ 1, 181, 46, 238, 128, 156, 114, 234, 166, 55, 12, 141, 245, 112, 94, 35, 193, 12, 96, 211, 90, 89, 35, 106, 71, 234, 10, 128, 185, 55, 92, 220, 34, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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