Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 339afc2fe31aadf2f12e18af8b53700afb3b64c592847e4865b8c2290314d391

Tx prefix hash: 55e00ad0b156102c1cdb1bd706ca6cb90c0483c047043347e35323a5e29ed995
Tx public key: dac3d21704fae9d2824b8e5d81703ded276344e32c920c4dd0c1c12fa5914df1
Timestamp: 1728324311 Timestamp [UCT]: 2024-10-07 18:05:11 Age [y:d:h:m:s]: 01:043:05:21:07
Block: 1126567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289280 RingCT/type: yes/0
Extra: 01dac3d21704fae9d2824b8e5d81703ded276344e32c920c4dd0c1c12fa5914df102110000000fe914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19937a4a280bad25b6c0c0ac226705a180b534b0d39950ea1052c65aadb4da2a 0.600000000000 1609362 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": 1126577, "vin": [ { "gen": { "height": 1126567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19937a4a280bad25b6c0c0ac226705a180b534b0d39950ea1052c65aadb4da2a" } } ], "extra": [ 1, 218, 195, 210, 23, 4, 250, 233, 210, 130, 75, 142, 93, 129, 112, 61, 237, 39, 99, 68, 227, 44, 146, 12, 77, 208, 193, 193, 47, 165, 145, 77, 241, 2, 17, 0, 0, 0, 15, 233, 20, 221, 21, 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