Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85d7ef94b35503c2c424f6fa794b15d40d0f3cbdb11523b285931329fe7f3dae

Tx prefix hash: ffb0c8cde0814d750dcfe2ed11c46141498577ec08bf65ba004cdd26fba653f4
Tx public key: 8a5393640d464c5314d28d9ff4f06c8dff42f1df6f88962d3737ce75b4fe3291
Timestamp: 1702757454 Timestamp [UCT]: 2023-12-16 20:10:54 Age [y:d:h:m:s]: 01:035:02:56:35
Block: 914611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286407 RingCT/type: yes/0
Extra: 018a5393640d464c5314d28d9ff4f06c8dff42f1df6f88962d3737ce75b4fe329102110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c83c3e5b457feb7e0c4eacac79a96deac52900a3f7e404b769983cf97e5aa83 0.600000000000 1371959 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": 914621, "vin": [ { "gen": { "height": 914611 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c83c3e5b457feb7e0c4eacac79a96deac52900a3f7e404b769983cf97e5aa83" } } ], "extra": [ 1, 138, 83, 147, 100, 13, 70, 76, 83, 20, 210, 141, 159, 244, 240, 108, 141, 255, 66, 241, 223, 111, 136, 150, 45, 55, 55, 206, 117, 180, 254, 50, 145, 2, 17, 0, 0, 0, 1, 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