Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54347e44f106070a4c5135a8ae52134add41d12346015b724824dfad86f15f8f

Tx prefix hash: 4a8c5e91ecc35cda66949b7838951bd28748415bb06aabc76d7029578874c0cc
Tx public key: 72bd1fa8b87ab9beb03aad1aba9fe9c7e7c6fbd7cebcd15a7a3fc903ad17b985
Timestamp: 1701979503 Timestamp [UCT]: 2023-12-07 20:05:03 Age [y:d:h:m:s]: 01:118:10:35:57
Block: 908158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345793 RingCT/type: yes/0
Extra: 0172bd1fa8b87ab9beb03aad1aba9fe9c7e7c6fbd7cebcd15a7a3fc903ad17b98502110000000175e3f0e9000000000000000000

1 output(s) for total of 0.601029132000 dcy

stealth address amount amount idx
00: 2bee8bc70f3ebe7b1ca09451f9573d8fbf4436473a2039be8f3cd9fbc0f8bc31 0.601029132000 1365183 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": 908168, "vin": [ { "gen": { "height": 908158 } } ], "vout": [ { "amount": 601029132, "target": { "key": "2bee8bc70f3ebe7b1ca09451f9573d8fbf4436473a2039be8f3cd9fbc0f8bc31" } } ], "extra": [ 1, 114, 189, 31, 168, 184, 122, 185, 190, 176, 58, 173, 26, 186, 159, 233, 199, 231, 198, 251, 215, 206, 188, 209, 90, 122, 63, 201, 3, 173, 23, 185, 133, 2, 17, 0, 0, 0, 1, 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