Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7ae42f5cd8d10b5397e868e4298ae423c2b23a50172a9d25f175977624566d6

Tx prefix hash: 214d1efc6d8daeb1153ba7f6d81bd4c3bbf6224174ed31255ffa8e11d5ecf312
Tx public key: 36ac2c486452e0b5f0965bc575d9c6cbbd14edf0e6d6dda10f0aca080f914153
Timestamp: 1706780081 Timestamp [UCT]: 2024-02-01 09:34:41 Age [y:d:h:m:s]: 01:129:21:54:25
Block: 947936 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353973 RingCT/type: yes/0
Extra: 0136ac2c486452e0b5f0965bc575d9c6cbbd14edf0e6d6dda10f0aca080f9141530211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2082b4a68306db8096f37ea3ae5f40ecf4215ef323bb6eec01ecfde293bd771 0.600000000000 1406296 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": 947946, "vin": [ { "gen": { "height": 947936 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2082b4a68306db8096f37ea3ae5f40ecf4215ef323bb6eec01ecfde293bd771" } } ], "extra": [ 1, 54, 172, 44, 72, 100, 82, 224, 181, 240, 150, 91, 197, 117, 217, 198, 203, 189, 20, 237, 240, 230, 214, 221, 161, 15, 10, 202, 8, 15, 145, 65, 83, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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