Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1ba07fe6b2c2be52953bd59005c3fcef96f81f9069f70a0e6b6b56d4af09e95

Tx prefix hash: 29d7492a626a4d88499dceb699372c8e37fe73a4ad90a72026098092e0ecaa64
Tx public key: 5408f502ebbeaaafdcb85cc5329e13ee2b263bbc86da4501d2840eab6767392d
Timestamp: 1738111896 Timestamp [UCT]: 2025-01-29 00:51:36 Age [y:d:h:m:s]: 00:322:20:06:20
Block: 1207301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228523 RingCT/type: yes/0
Extra: 015408f502ebbeaaafdcb85cc5329e13ee2b263bbc86da4501d2840eab6767392d0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b861e24d6548b5e9696e709e0e074b8bf0a168d4769f764d2a34cc00a94e2b2a 0.600000000000 1694024 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": 1207311, "vin": [ { "gen": { "height": 1207301 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b861e24d6548b5e9696e709e0e074b8bf0a168d4769f764d2a34cc00a94e2b2a" } } ], "extra": [ 1, 84, 8, 245, 2, 235, 190, 170, 175, 220, 184, 92, 197, 50, 158, 19, 238, 43, 38, 59, 188, 134, 218, 69, 1, 210, 132, 14, 171, 103, 103, 57, 45, 2, 17, 0, 0, 0, 2, 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