Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1da85eb8c558aba0229e023591cab80553e48a7a4f9afe5736cd76b356f80b5e

Tx prefix hash: 2ebfec564979baf0042bc9e06309c418ba5b79cc5a2c81dc3953e5c8686a5b31
Tx public key: 0cbc01c7a439d1b3213efc59b42d00fc7ec38faa492b61e1d0c993e09652c5c7
Timestamp: 1726437991 Timestamp [UCT]: 2024-09-15 22:06:31 Age [y:d:h:m:s]: 00:182:14:50:03
Block: 1110930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130358 RingCT/type: yes/0
Extra: 010cbc01c7a439d1b3213efc59b42d00fc7ec38faa492b61e1d0c993e09652c5c702110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f4630ce75ab71d3a53f0fd12fb7e12ea67187f8f02cba55543bf626167b313e 0.600000000000 1589711 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": 1110940, "vin": [ { "gen": { "height": 1110930 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f4630ce75ab71d3a53f0fd12fb7e12ea67187f8f02cba55543bf626167b313e" } } ], "extra": [ 1, 12, 188, 1, 199, 164, 57, 209, 179, 33, 62, 252, 89, 180, 45, 0, 252, 126, 195, 143, 170, 73, 43, 97, 225, 208, 201, 147, 224, 150, 82, 197, 199, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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