Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53c31713aeadc77ecab81f5c2625ab3dad9e8eb32a2532ac3bef8c502795c104

Tx prefix hash: ad104f4bedad078cc2aaa77d40693740ec213e3ce71675752aacfa11aeb2fd2c
Tx public key: bd38393b5fc85e1d32c3aca8f726cb00518ab89761ea702b9c122cc1e05898e4
Timestamp: 1708234756 Timestamp [UCT]: 2024-02-18 05:39:16 Age [y:d:h:m:s]: 01:095:06:35:15
Block: 960017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329160 RingCT/type: yes/0
Extra: 01bd38393b5fc85e1d32c3aca8f726cb00518ab89761ea702b9c122cc1e05898e40211000000033f0590f7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b14fb01ceb951e3e5951c7eaa7f0015611a968f4f9b0eb373000b6a7e7e3102 0.600000000000 1419576 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": 960027, "vin": [ { "gen": { "height": 960017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b14fb01ceb951e3e5951c7eaa7f0015611a968f4f9b0eb373000b6a7e7e3102" } } ], "extra": [ 1, 189, 56, 57, 59, 95, 200, 94, 29, 50, 195, 172, 168, 247, 38, 203, 0, 81, 138, 184, 151, 97, 234, 112, 43, 156, 18, 44, 193, 224, 88, 152, 228, 2, 17, 0, 0, 0, 3, 63, 5, 144, 247, 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