Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0e47e0494f411217c4991bb537a86b1c7b5a52a30d3ee97aa541ea8111306a6

Tx prefix hash: 3a2f35dd7956cff815aae698316a146082a6555691b0ec38ddd6d45daf55bfaf
Tx public key: 8af48a7df6b846b51058ad0c307490929eab670a782811b5a46e56ee01ec14d2
Timestamp: 1719774915 Timestamp [UCT]: 2024-06-30 19:15:15 Age [y:d:h:m:s]: 01:131:13:39:18
Block: 1055681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352575 RingCT/type: yes/0
Extra: 018af48a7df6b846b51058ad0c307490929eab670a782811b5a46e56ee01ec14d2021100000004ddd3db91000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 055defb0cc76aa1116ea016fa48b432267b489856b76ad0bebe06ec9f061ee0d 0.600000000000 1526086 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": 1055691, "vin": [ { "gen": { "height": 1055681 } } ], "vout": [ { "amount": 600000000, "target": { "key": "055defb0cc76aa1116ea016fa48b432267b489856b76ad0bebe06ec9f061ee0d" } } ], "extra": [ 1, 138, 244, 138, 125, 246, 184, 70, 181, 16, 88, 173, 12, 48, 116, 144, 146, 158, 171, 103, 10, 120, 40, 17, 181, 164, 110, 86, 238, 1, 236, 20, 210, 2, 17, 0, 0, 0, 4, 221, 211, 219, 145, 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