Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c5f3b482c3494b129a20cd4b9ac545535ebc88fcb02827e1b997607bb4004d3

Tx prefix hash: a115e47f98fa0a5b38ea10b9f66f9a990e04cf466f6e87a00d40f6be921e2da6
Tx public key: 87afac5f66b3eba1114ddac0e98f972634850280cb613820933e5a2c1e06dbe3
Timestamp: 1736660360 Timestamp [UCT]: 2025-01-12 05:39:20 Age [y:d:h:m:s]: 00:160:06:11:52
Block: 1195534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114201 RingCT/type: yes/0
Extra: 0187afac5f66b3eba1114ddac0e98f972634850280cb613820933e5a2c1e06dbe30211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 322a84b54ed84ce57b6112639a82f9e8cb39940cac6e09bc99023ba01aaece13 0.600000000000 1682125 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": 1195544, "vin": [ { "gen": { "height": 1195534 } } ], "vout": [ { "amount": 600000000, "target": { "key": "322a84b54ed84ce57b6112639a82f9e8cb39940cac6e09bc99023ba01aaece13" } } ], "extra": [ 1, 135, 175, 172, 95, 102, 179, 235, 161, 17, 77, 218, 192, 233, 143, 151, 38, 52, 133, 2, 128, 203, 97, 56, 32, 147, 62, 90, 44, 30, 6, 219, 227, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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