Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd039ce952474e231968e50f88f55bb0f06f2b5b9cd1b4c3d9ac200fc87841b6

Tx prefix hash: 65ec740311d778e931dd30eadb6007a528714f68d9859d64ce14fc5e8aeee4af
Tx public key: 0f8bf32629aa71d6b00eb62ecbd3ad67eb711db7abe55cdb9a68f2fb848275a6
Timestamp: 1736722930 Timestamp [UCT]: 2025-01-12 23:02:10 Age [y:d:h:m:s]: 00:104:21:05:28
Block: 1196052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74753 RingCT/type: yes/0
Extra: 010f8bf32629aa71d6b00eb62ecbd3ad67eb711db7abe55cdb9a68f2fb848275a60211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fb0ddb7cc8f47eb09c2d447623e69459fbb196e5435ad156ab9a81905238ab9 0.600000000000 1682649 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": 1196062, "vin": [ { "gen": { "height": 1196052 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fb0ddb7cc8f47eb09c2d447623e69459fbb196e5435ad156ab9a81905238ab9" } } ], "extra": [ 1, 15, 139, 243, 38, 41, 170, 113, 214, 176, 14, 182, 46, 203, 211, 173, 103, 235, 113, 29, 183, 171, 229, 92, 219, 154, 104, 242, 251, 132, 130, 117, 166, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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