Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55bf768a9532336a5144fbc88fc472841b9f40f23d81b7e26dcfcbad7d18e1cb

Tx prefix hash: a1f40097f67f2f2cc202e2a64944eeccf5f60006284d60693bfeceef6c37f1a4
Tx public key: b0abb213e19bb75119bac38aec32118f7a5cf9f2f22cc580c6a33c61bee8c9b7
Timestamp: 1717540102 Timestamp [UCT]: 2024-06-04 22:28:22 Age [y:d:h:m:s]: 01:159:02:05:07
Block: 1037176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372269 RingCT/type: yes/0
Extra: 01b0abb213e19bb75119bac38aec32118f7a5cf9f2f22cc580c6a33c61bee8c9b702110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67f01685136ce68e17905ed07d5412ad16baa4e7fba3bfe0f06d8d518131582f 0.600000000000 1505707 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": 1037186, "vin": [ { "gen": { "height": 1037176 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67f01685136ce68e17905ed07d5412ad16baa4e7fba3bfe0f06d8d518131582f" } } ], "extra": [ 1, 176, 171, 178, 19, 225, 155, 183, 81, 25, 186, 195, 138, 236, 50, 17, 143, 122, 92, 249, 242, 242, 44, 197, 128, 198, 163, 60, 97, 190, 232, 201, 183, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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