Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec6b74b08c9a4214f507510c29310e3ee77aba3c9970588d87dee2af6aff97b3

Tx prefix hash: 1be9e51eecb9dbe0e2ce21a5a53da8bd44ee20080c4bdc09e960e6f2a2f715a2
Tx public key: 696276a8986a978741cc52a733297eb7aa308f5bdf452174c5fc933fc7fc8eae
Timestamp: 1751639448 Timestamp [UCT]: 2025-07-04 14:30:48 Age [y:d:h:m:s]: 00:139:08:45:32
Block: 1318653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97902 RingCT/type: yes/0
Extra: 01696276a8986a978741cc52a733297eb7aa308f5bdf452174c5fc933fc7fc8eae021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed57710d434d98d9540abd2d3910f69c92d96a593bb3c8d49bb5b34ad2f500b1 0.600000000000 1806338 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": 1318663, "vin": [ { "gen": { "height": 1318653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed57710d434d98d9540abd2d3910f69c92d96a593bb3c8d49bb5b34ad2f500b1" } } ], "extra": [ 1, 105, 98, 118, 168, 152, 106, 151, 135, 65, 204, 82, 167, 51, 41, 126, 183, 170, 48, 143, 91, 223, 69, 33, 116, 197, 252, 147, 63, 199, 252, 142, 174, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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