Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63e1be120a2c0116c9240e622047789b29ae15b4fa4c078b9c83e6119535f1df

Tx prefix hash: ff8843972be8f950c097baf6188f631b6fe508febe31022adc5be5abd3a5a737
Tx public key: 316cb6ab3da6bda52201e8e7e8b5ee73162e589192fa3b1a02202bec80dc2403
Timestamp: 1713729966 Timestamp [UCT]: 2024-04-21 20:06:06 Age [y:d:h:m:s]: 00:203:09:34:12
Block: 1005563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145607 RingCT/type: yes/0
Extra: 01316cb6ab3da6bda52201e8e7e8b5ee73162e589192fa3b1a02202bec80dc24030211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ef95887b9271d5711e7601eb15ca7632f7c41367811d3df00cf164e6d62df23 0.600000000000 1466297 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": 1005573, "vin": [ { "gen": { "height": 1005563 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ef95887b9271d5711e7601eb15ca7632f7c41367811d3df00cf164e6d62df23" } } ], "extra": [ 1, 49, 108, 182, 171, 61, 166, 189, 165, 34, 1, 232, 231, 232, 181, 238, 115, 22, 46, 88, 145, 146, 250, 59, 26, 2, 32, 43, 236, 128, 220, 36, 3, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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