Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3baa596921586e512f5a99a63f6813aad6e9997946aea46dce0d7c4ff2e21c0d

Tx prefix hash: 7ac21b80526437f2919b8992846a215beea1fb0b7d6b976f0aff507bef114358
Tx public key: dd2938ac0570595343a5a6e0f2961889115c810a958fdddcc1e84a4cc25b3673
Timestamp: 1737232658 Timestamp [UCT]: 2025-01-18 20:37:38 Age [y:d:h:m:s]: 00:155:02:29:49
Block: 1200241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110501 RingCT/type: yes/0
Extra: 01dd2938ac0570595343a5a6e0f2961889115c810a958fdddcc1e84a4cc25b36730211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 819633a7b6bbbe21b375c1d7f4a615ccb92dab0ec3fe7603460330843c62dcdb 0.600000000000 1686884 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": 1200251, "vin": [ { "gen": { "height": 1200241 } } ], "vout": [ { "amount": 600000000, "target": { "key": "819633a7b6bbbe21b375c1d7f4a615ccb92dab0ec3fe7603460330843c62dcdb" } } ], "extra": [ 1, 221, 41, 56, 172, 5, 112, 89, 83, 67, 165, 166, 224, 242, 150, 24, 137, 17, 92, 129, 10, 149, 143, 221, 220, 193, 232, 74, 76, 194, 91, 54, 115, 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