Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18e8ef6c37e3092441cff8d236561158d9c27b31dfe17a320c4469bce55ae5dc

Tx prefix hash: a9a070ffc4479ac653b16c42249441096de4cbcc612b793de33e210495bff0b5
Tx public key: e29439f3c99aa321ae12fa0dc361e69db2b7e55a67a0e60b9682411390919f2b
Timestamp: 1707390202 Timestamp [UCT]: 2024-02-08 11:03:22 Age [y:d:h:m:s]: 01:095:01:07:30
Block: 953007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329003 RingCT/type: yes/0
Extra: 01e29439f3c99aa321ae12fa0dc361e69db2b7e55a67a0e60b9682411390919f2b0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b4bd9dfc72d99858e5139898377d1498da2245033eb1f93e206d98d086544b0 0.600000000000 1412163 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": 953017, "vin": [ { "gen": { "height": 953007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b4bd9dfc72d99858e5139898377d1498da2245033eb1f93e206d98d086544b0" } } ], "extra": [ 1, 226, 148, 57, 243, 201, 154, 163, 33, 174, 18, 250, 13, 195, 97, 230, 157, 178, 183, 229, 90, 103, 160, 230, 11, 150, 130, 65, 19, 144, 145, 159, 43, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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