Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b812ec19137bcb5a7732ea4548d491d7fa29a5aa8ae9100da9e788b0b8a16ba4

Tx prefix hash: db349065f791e09630bfdc50b09a8805fcfee6b253ab197c1741a3c30501268e
Tx public key: d4014e2f5350c9163fa488abdc645412fb8327648272dc0ccf612bd695d6d793
Timestamp: 1700983453 Timestamp [UCT]: 2023-11-26 07:24:13 Age [y:d:h:m:s]: 01:343:16:41:21
Block: 899890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 504515 RingCT/type: yes/0
Extra: 01d4014e2f5350c9163fa488abdc645412fb8327648272dc0ccf612bd695d6d793021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.640163416000 dcy

stealth address amount amount idx
00: 39701e63f259764b4d91d97de7b160a85888e834f065357843ce6901ef469bd8 0.640163416000 1356359 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": 899900, "vin": [ { "gen": { "height": 899890 } } ], "vout": [ { "amount": 640163416, "target": { "key": "39701e63f259764b4d91d97de7b160a85888e834f065357843ce6901ef469bd8" } } ], "extra": [ 1, 212, 1, 78, 47, 83, 80, 201, 22, 63, 164, 136, 171, 220, 100, 84, 18, 251, 131, 39, 100, 130, 114, 220, 12, 207, 97, 43, 214, 149, 214, 215, 147, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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