Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aed9e60abb5efaf44427d55a6ac01956f0783d2a5aa524a6cf588d3cb23c6390

Tx prefix hash: 3e9b6239ab0d35ba50a413a36fb75a1fd781bcf1a4bedbd6bab37e3964741685
Tx public key: 2e5f975e3ae7a85715e9b1893cbc53fd342fc45829986e39f9b3711c28e61461
Timestamp: 1702586248 Timestamp [UCT]: 2023-12-14 20:37:28 Age [y:d:h:m:s]: 01:178:09:31:36
Block: 913176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388699 RingCT/type: yes/0
Extra: 012e5f975e3ae7a85715e9b1893cbc53fd342fc45829986e39f9b3711c28e6146102110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4df1222ccc74e62b8406e92b9a024c972f66e8c91fc25b9a1d1302e8b031c939 0.600000000000 1370422 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": 913186, "vin": [ { "gen": { "height": 913176 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4df1222ccc74e62b8406e92b9a024c972f66e8c91fc25b9a1d1302e8b031c939" } } ], "extra": [ 1, 46, 95, 151, 94, 58, 231, 168, 87, 21, 233, 177, 137, 60, 188, 83, 253, 52, 47, 196, 88, 41, 152, 110, 57, 249, 179, 113, 28, 40, 230, 20, 97, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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