Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e93735a4a946af8dda066889f31d9860f4b55c24f8aef376269edc118aaa3a0

Tx prefix hash: c3592a77b27bfe2e01c2028dd45545d607adf9ffaaf919029606795c14f17c69
Tx public key: 48ec0eadb3b6ccfb645d2bef0eb78fbc584d9a4e993d87f48661ff930af2f09b
Timestamp: 1741406716 Timestamp [UCT]: 2025-03-08 04:05:16 Age [y:d:h:m:s]: 00:258:07:56:04
Block: 1234562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182371 RingCT/type: yes/0
Extra: 0148ec0eadb3b6ccfb645d2bef0eb78fbc584d9a4e993d87f48661ff930af2f09b021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f613af3d6f8601edf363b2b8aee77b0109524b7be87cf356f330448b3a46b0c4 0.600000000000 1721491 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": 1234572, "vin": [ { "gen": { "height": 1234562 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f613af3d6f8601edf363b2b8aee77b0109524b7be87cf356f330448b3a46b0c4" } } ], "extra": [ 1, 72, 236, 14, 173, 179, 182, 204, 251, 100, 93, 43, 239, 14, 183, 143, 188, 88, 77, 154, 78, 153, 61, 135, 244, 134, 97, 255, 147, 10, 242, 240, 155, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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