Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b759ebd4a582e58c9ab046b3affd5a0fb4faa68888a0b4523089dd4f327636a0

Tx prefix hash: 0161fc86e6a743f00281974a9be7552da86587c91dca9ae63484305467813d4e
Tx public key: 04e7d6e2e61dfa8557cd7c983feb732bfc50de86b13e927776105edf8ca7b15c
Timestamp: 1736261468 Timestamp [UCT]: 2025-01-07 14:51:08 Age [y:d:h:m:s]: 00:072:12:37:03
Block: 1192239 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51625 RingCT/type: yes/0
Extra: 0104e7d6e2e61dfa8557cd7c983feb732bfc50de86b13e927776105edf8ca7b15c0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f38f71ad58813d6d3b543af513d93417d59ef14a1db9ba05d3b537d18462cab3 0.600000000000 1678788 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": 1192249, "vin": [ { "gen": { "height": 1192239 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f38f71ad58813d6d3b543af513d93417d59ef14a1db9ba05d3b537d18462cab3" } } ], "extra": [ 1, 4, 231, 214, 226, 230, 29, 250, 133, 87, 205, 124, 152, 63, 235, 115, 43, 252, 80, 222, 134, 177, 62, 146, 119, 118, 16, 94, 223, 140, 167, 177, 92, 2, 17, 0, 0, 0, 1, 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