Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4cfa2a5c058e82f0fd4cd49b2705ceaa11064b762bf7e20ab3642c95286b685c

Tx prefix hash: d0ea3db8c4d1811bcce4519a6a21f6a20b83cdbed2febd04880c9eb52bdafe5c
Tx public key: be39533ef80f8350ae92a855c1a0c8b1fbd3e0c64872fd9b640c0107a5e92ec4
Timestamp: 1718075459 Timestamp [UCT]: 2024-06-11 03:10:59 Age [y:d:h:m:s]: 00:261:17:29:39
Block: 1041609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186994 RingCT/type: yes/0
Extra: 01be39533ef80f8350ae92a855c1a0c8b1fbd3e0c64872fd9b640c0107a5e92ec40211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f7eff37847a0da4e98539548bf9340e20a28e24c87b887ca082e815967e3710 0.600000000000 1510326 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": 1041619, "vin": [ { "gen": { "height": 1041609 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f7eff37847a0da4e98539548bf9340e20a28e24c87b887ca082e815967e3710" } } ], "extra": [ 1, 190, 57, 83, 62, 248, 15, 131, 80, 174, 146, 168, 85, 193, 160, 200, 177, 251, 211, 224, 198, 72, 114, 253, 155, 100, 12, 1, 7, 165, 233, 46, 196, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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