Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 909fb0bd05fe7c3c54c34f89fb4eb49748db9f61ad2c143b7301d33cbe691e82

Tx prefix hash: 1f47a6a87f0646200b30b4b4a57fa17cbc1cbfeaedbb7ba658abf7b85a0a2c9d
Tx public key: b54d9835b8a39d59df4485c4995dca0835b675d4019a58df209ee7c72edd3136
Timestamp: 1700050242 Timestamp [UCT]: 2023-11-15 12:10:42 Age [y:d:h:m:s]: 01:067:22:47:47
Block: 892160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309931 RingCT/type: yes/0
Extra: 01b54d9835b8a39d59df4485c4995dca0835b675d4019a58df209ee7c72edd313602110000000375e3f0e9000000000000000000

1 output(s) for total of 0.679052827000 dcy

stealth address amount amount idx
00: 0a40171a851e8e0d30a00efd96e5d01a4f2dd8155e0113e0d6925b463743f4c5 0.679052827000 1348239 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": 892170, "vin": [ { "gen": { "height": 892160 } } ], "vout": [ { "amount": 679052827, "target": { "key": "0a40171a851e8e0d30a00efd96e5d01a4f2dd8155e0113e0d6925b463743f4c5" } } ], "extra": [ 1, 181, 77, 152, 53, 184, 163, 157, 89, 223, 68, 133, 196, 153, 93, 202, 8, 53, 182, 117, 212, 1, 154, 88, 223, 32, 158, 231, 199, 46, 221, 49, 54, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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