Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a441a1da4239e38b49c7082678d22d6ab11296c583e321d23a45c5a08d3e746

Tx prefix hash: 929ecf01fb79d74ea729c779be47c4e51d9be488cc34696e601a829e170808fe
Tx public key: a7604be75e7f2ec4edd8d01688632145a0608f44e97e0e789a8c5cb868f5b7d0
Timestamp: 1736661163 Timestamp [UCT]: 2025-01-12 05:52:43 Age [y:d:h:m:s]: 00:061:20:04:34
Block: 1195537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43993 RingCT/type: yes/0
Extra: 01a7604be75e7f2ec4edd8d01688632145a0608f44e97e0e789a8c5cb868f5b7d00211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8824f8daec5a2d3ed4d410d2fb626ce39a431a309b40911504433c693db3ab8f 0.600000000000 1682128 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": 1195547, "vin": [ { "gen": { "height": 1195537 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8824f8daec5a2d3ed4d410d2fb626ce39a431a309b40911504433c693db3ab8f" } } ], "extra": [ 1, 167, 96, 75, 231, 94, 127, 46, 196, 237, 216, 208, 22, 136, 99, 33, 69, 160, 96, 143, 68, 233, 126, 14, 120, 154, 140, 92, 184, 104, 245, 183, 208, 2, 17, 0, 0, 0, 2, 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