Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bed6793d2d8054d0001c3e52da96c3b54d7701c4f5fc8a0c5da419d820141957

Tx prefix hash: 1699525d9d3082fd28759b01417bd6b7a9e92c92434e1f8fa98f077aff5bace2
Tx public key: bf8e5da6bad3a16e0b345939b1f7a8b11411a825161249a2dbee483b44161789
Timestamp: 1704660029 Timestamp [UCT]: 2024-01-07 20:40:29 Age [y:d:h:m:s]: 01:135:03:25:58
Block: 930354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357745 RingCT/type: yes/0
Extra: 01bf8e5da6bad3a16e0b345939b1f7a8b11411a825161249a2dbee483b441617890211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64c4630f05851c2ef42338af771320e4be7a5a77334b65197825da0ed47f949d 0.600000000000 1388236 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": 930364, "vin": [ { "gen": { "height": 930354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64c4630f05851c2ef42338af771320e4be7a5a77334b65197825da0ed47f949d" } } ], "extra": [ 1, 191, 142, 93, 166, 186, 211, 161, 110, 11, 52, 89, 57, 177, 247, 168, 177, 20, 17, 168, 37, 22, 18, 73, 162, 219, 238, 72, 59, 68, 22, 23, 137, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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