Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e2544f399c3b76d95d99d1f12feda54b98122253904f0c99db15e4739185c20

Tx prefix hash: d775652ca1abe5deee8029b8f4ddf3d8fd4cb7cf61cbb3c7075f8a21a3037d65
Tx public key: d8a04a5f7c74c9212b42d5b86a7a3b9aeaf54080480661747697dccdcb935034
Timestamp: 1745981077 Timestamp [UCT]: 2025-04-30 02:44:37 Age [y:d:h:m:s]: 00:013:03:05:32
Block: 1272436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9385 RingCT/type: yes/0
Extra: 01d8a04a5f7c74c9212b42d5b86a7a3b9aeaf54080480661747697dccdcb93503402110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2212374aa3516aff0e95d750d4fad45826c3d9a17cff875726cfa62f594fe53 0.600000000000 1759711 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": 1272446, "vin": [ { "gen": { "height": 1272436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2212374aa3516aff0e95d750d4fad45826c3d9a17cff875726cfa62f594fe53" } } ], "extra": [ 1, 216, 160, 74, 95, 124, 116, 201, 33, 43, 66, 213, 184, 106, 122, 59, 154, 234, 245, 64, 128, 72, 6, 97, 116, 118, 151, 220, 205, 203, 147, 80, 52, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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