Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49f39fd278861e49a313249b14a5f63eac753fb9eea32b83d8f5144b60e6f094

Tx prefix hash: 6e9df36adcb11d7fb23936d3aadd6b3f09a6fbbc3fbf574e7de5ac0381c6b3ce
Tx public key: c40bbbc8eb43a280d343a438b7b9786c50b46a6bc49dd7fd0c849eef33e5bc26
Timestamp: 1712166464 Timestamp [UCT]: 2024-04-03 17:47:44 Age [y:d:h:m:s]: 00:202:20:44:51
Block: 992589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145300 RingCT/type: yes/0
Extra: 01c40bbbc8eb43a280d343a438b7b9786c50b46a6bc49dd7fd0c849eef33e5bc2602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4c80d63e1c0e2c6f2ffc6fcc87aa952cc52a1d46be344db7e67269d75d1494c 0.600000000000 1452949 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": 992599, "vin": [ { "gen": { "height": 992589 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4c80d63e1c0e2c6f2ffc6fcc87aa952cc52a1d46be344db7e67269d75d1494c" } } ], "extra": [ 1, 196, 11, 187, 200, 235, 67, 162, 128, 211, 67, 164, 56, 183, 185, 120, 108, 80, 180, 106, 107, 196, 157, 215, 253, 12, 132, 158, 239, 51, 229, 188, 38, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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