Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cea8a8211e012821164a9aec795f218f6ef2e1b1f24916309cb2072ff2f42440

Tx prefix hash: 8d0c2e48c2c6bdf25ae28a87d1ce51f99be60932748fe2a8c6944f90c6ec8d2b
Tx public key: 4445aeb5e802fbedc60533392d2bdf29a229dbcc65173c70451d544818ee2ac7
Timestamp: 1684853207 Timestamp [UCT]: 2023-05-23 14:46:47 Age [y:d:h:m:s]: 01:241:09:14:32
Block: 766428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433911 RingCT/type: yes/0
Extra: 014445aeb5e802fbedc60533392d2bdf29a229dbcc65173c70451d544818ee2ac7021100000001faf35c9c000000000000000000

1 output(s) for total of 1.772172756000 dcy

stealth address amount amount idx
00: 5df1a090333b30f33e005619b0b5de193fcd8a31b67b956191a615483b6e557e 1.772172756000 1215467 of 0

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": 766438, "vin": [ { "gen": { "height": 766428 } } ], "vout": [ { "amount": 1772172756, "target": { "key": "5df1a090333b30f33e005619b0b5de193fcd8a31b67b956191a615483b6e557e" } } ], "extra": [ 1, 68, 69, 174, 181, 232, 2, 251, 237, 198, 5, 51, 57, 45, 43, 223, 41, 162, 41, 219, 204, 101, 23, 60, 112, 69, 29, 84, 72, 24, 238, 42, 199, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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