Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6ea2d3dde761120ef85f82bdbf3322cec54a5d1ae30bff3ebe0a2f9433efa69

Tx prefix hash: 867e4c818f35722d07105a053d37cc7eaff0aeeec9ccb8479e48f9c50739e400
Tx public key: 83aaf2c083e6f8ec19c9f2ae25cb12ec045bfdf2e662a47383517402030e24d1
Timestamp: 1702487942 Timestamp [UCT]: 2023-12-13 17:19:02 Age [y:d:h:m:s]: 01:329:11:28:35
Block: 912375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494322 RingCT/type: yes/0
Extra: 0183aaf2c083e6f8ec19c9f2ae25cb12ec045bfdf2e662a47383517402030e24d102110000000375e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b6968c28fff1124d7b19ed1b37b0e31f47beea1ec8a8aafd06f8eb0ecde4e2f 0.600000000000 1369601 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": 912385, "vin": [ { "gen": { "height": 912375 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b6968c28fff1124d7b19ed1b37b0e31f47beea1ec8a8aafd06f8eb0ecde4e2f" } } ], "extra": [ 1, 131, 170, 242, 192, 131, 230, 248, 236, 25, 201, 242, 174, 37, 203, 18, 236, 4, 91, 253, 242, 230, 98, 164, 115, 131, 81, 116, 2, 3, 14, 36, 209, 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