Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b002d531af8452b0cd1f4b377f31f237f18fbd8fa5af572311bcb1832e6b9aab

Tx prefix hash: 5853485dc3d1682a8b5947f25cbaa4ba784886c1ab92555e9e05571c212718ae
Tx public key: d9520e2066a17db6023c9d0f27ca10d4733285b163cef54e71e7f54d8f4b65e3
Timestamp: 1577206702 Timestamp [UCT]: 2019-12-24 16:58:22 Age [y:d:h:m:s]: 05:005:23:22:30
Block: 30899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1154222 RingCT/type: yes/0
Extra: 01d9520e2066a17db6023c9d0f27ca10d4733285b163cef54e71e7f54d8f4b65e3021100000024c3a1a09f000000000000000000

1 output(s) for total of 484.863673110000 dcy

stealth address amount amount idx
00: 3a9bbe33b32060f4bfe469dc9c2ea6c51d13e1457d472f3e2cbeae7ba4a8c409 484.863673110000 50993 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": 30909, "vin": [ { "gen": { "height": 30899 } } ], "vout": [ { "amount": 484863673110, "target": { "key": "3a9bbe33b32060f4bfe469dc9c2ea6c51d13e1457d472f3e2cbeae7ba4a8c409" } } ], "extra": [ 1, 217, 82, 14, 32, 102, 161, 125, 182, 2, 60, 157, 15, 39, 202, 16, 212, 115, 50, 133, 177, 99, 206, 245, 78, 113, 231, 245, 77, 143, 75, 101, 227, 2, 17, 0, 0, 0, 36, 195, 161, 160, 159, 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