Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 733124c2070580c1f4c6e82b12e8f29377f264fccbcb8d278fb9dd8ac79bcdad

Tx prefix hash: e7f982eca50ac9d369e78d7e6db6bf699d8006d8126d0f38292a5fc0fee8fd14
Tx public key: bee175e20b5fe9964cd94bb761ee9e30520bb6701cae40e4a0ac5ae1c3e2b722
Timestamp: 1721270791 Timestamp [UCT]: 2024-07-18 02:46:31 Age [y:d:h:m:s]: 00:251:00:50:08
Block: 1068107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179304 RingCT/type: yes/0
Extra: 01bee175e20b5fe9964cd94bb761ee9e30520bb6701cae40e4a0ac5ae1c3e2b72202110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: add7d5445cbd71d51eea317e965cdef2308f94e5027213fd076ccfb683fdb064 0.600000000000 1539122 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": 1068117, "vin": [ { "gen": { "height": 1068107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "add7d5445cbd71d51eea317e965cdef2308f94e5027213fd076ccfb683fdb064" } } ], "extra": [ 1, 190, 225, 117, 226, 11, 95, 233, 150, 76, 217, 75, 183, 97, 238, 158, 48, 82, 11, 182, 112, 28, 174, 64, 228, 160, 172, 90, 225, 195, 226, 183, 34, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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