Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19398065a35a1d2fc753de968cad28239fc969ad75a671caa9c9deb8d61738f9

Tx prefix hash: 9b0fc44c2e139be2d35827eb201cca250a0c1ae0701f4971b6d6adc8e07423f5
Tx public key: b0c2b8542924520b03f8d83a9e9a64cac8f75dc7825ac8e122348b8fbb6aaa16
Timestamp: 1734588199 Timestamp [UCT]: 2024-12-19 06:03:19 Age [y:d:h:m:s]: 00:095:14:18:36
Block: 1178410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68074 RingCT/type: yes/0
Extra: 01b0c2b8542924520b03f8d83a9e9a64cac8f75dc7825ac8e122348b8fbb6aaa160211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa203ad382ae67db5f6088e81b2769a45163e4312817158d920e9f59a64cdaac 0.600000000000 1664797 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": 1178420, "vin": [ { "gen": { "height": 1178410 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa203ad382ae67db5f6088e81b2769a45163e4312817158d920e9f59a64cdaac" } } ], "extra": [ 1, 176, 194, 184, 84, 41, 36, 82, 11, 3, 248, 216, 58, 158, 154, 100, 202, 200, 247, 93, 199, 130, 90, 200, 225, 34, 52, 139, 143, 187, 106, 170, 22, 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