Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 614ca167eba93703ec57cb919e8b3db2bb6058e7b42198118beaa23d2bc4c06b

Tx prefix hash: edd749ef086ff194a32cd96734d40912d7c784ca90bef7633e5229f0417bf64b
Tx public key: 3b8ee19ac79cc49df384f42c7e2e34ed0509ad7131dfa20d3c3211eddf4b1a29
Timestamp: 1703049842 Timestamp [UCT]: 2023-12-20 05:24:02 Age [y:d:h:m:s]: 01:147:10:43:51
Block: 917030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366532 RingCT/type: yes/0
Extra: 013b8ee19ac79cc49df384f42c7e2e34ed0509ad7131dfa20d3c3211eddf4b1a29021100000004e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4262c89edb115c3c155791c5034691bd180c24a19dc5e0f0673c0e25df7ec2e8 0.600000000000 1374594 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": 917040, "vin": [ { "gen": { "height": 917030 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4262c89edb115c3c155791c5034691bd180c24a19dc5e0f0673c0e25df7ec2e8" } } ], "extra": [ 1, 59, 142, 225, 154, 199, 156, 196, 157, 243, 132, 244, 44, 126, 46, 52, 237, 5, 9, 173, 113, 49, 223, 162, 13, 60, 50, 17, 237, 223, 75, 26, 41, 2, 17, 0, 0, 0, 4, 228, 187, 107, 131, 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