Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7009f1cebd0ef8d6ee14e9bf3b5a6388cc4c2065d46c97664637da2f49ffa6d2

Tx prefix hash: 0c9d53d514ab38d8ca17613cb0aabc6c674d82666d38a7541c33a463d287acce
Tx public key: dc213f04dc02f8f4e9148c6f42d8a3102a26a4c2d73f4aed7efd28b2076bd26c
Timestamp: 1703989765 Timestamp [UCT]: 2023-12-31 02:29:25 Age [y:d:h:m:s]: 01:101:07:50:10
Block: 924817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333532 RingCT/type: yes/0
Extra: 01dc213f04dc02f8f4e9148c6f42d8a3102a26a4c2d73f4aed7efd28b2076bd26c02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cb94f74df4c2e91fad9c995a26186b6a875068ca1173a8712aff06e657251a0 0.600000000000 1382575 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": 924827, "vin": [ { "gen": { "height": 924817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cb94f74df4c2e91fad9c995a26186b6a875068ca1173a8712aff06e657251a0" } } ], "extra": [ 1, 220, 33, 63, 4, 220, 2, 248, 244, 233, 20, 140, 111, 66, 216, 163, 16, 42, 38, 164, 194, 215, 63, 74, 237, 126, 253, 40, 178, 7, 107, 210, 108, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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