Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef3167cd741fa477cf3d7d0a3b37e3e42d3eefc6cb43c1a648112402d7629309

Tx prefix hash: f14272b4dc6036120cf4119f3dc10e472e2044e29b8262f92f9f1738b3b25d7b
Tx public key: 98e4bfbb9bba6ce9f20046e33c6d5b6c8ace303404b479844f6de1cce2053d29
Timestamp: 1741267221 Timestamp [UCT]: 2025-03-06 13:20:21 Age [y:d:h:m:s]: 00:260:09:51:54
Block: 1233420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183847 RingCT/type: yes/0
Extra: 0198e4bfbb9bba6ce9f20046e33c6d5b6c8ace303404b479844f6de1cce2053d29021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67980e8e28bb6d01e93c835057749814b1e2e75b99ee88d6d0e244523c6e410d 0.600000000000 1720341 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": 1233430, "vin": [ { "gen": { "height": 1233420 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67980e8e28bb6d01e93c835057749814b1e2e75b99ee88d6d0e244523c6e410d" } } ], "extra": [ 1, 152, 228, 191, 187, 155, 186, 108, 233, 242, 0, 70, 227, 60, 109, 91, 108, 138, 206, 48, 52, 4, 180, 121, 132, 79, 109, 225, 204, 226, 5, 61, 41, 2, 17, 0, 0, 0, 3, 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