Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c657766eb6f6f4e7780583b2f2a0fa592c85b76d2e0a431a3de6aa66cbb79199

Tx prefix hash: 9a18485cb593aa6a326f51dfb801649b0cc1e52c716cda65de82bbbe73dd324c
Tx public key: 8bc107ae483ec80c9aef1d17752fec974b91636431cba02c59555b21d7dc01f7
Timestamp: 1714072518 Timestamp [UCT]: 2024-04-25 19:15:18 Age [y:d:h:m:s]: 00:217:01:11:47
Block: 1008408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155383 RingCT/type: yes/0
Extra: 018bc107ae483ec80c9aef1d17752fec974b91636431cba02c59555b21d7dc01f70211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5fe7f6a5ebdab08411b36f4cdcff1d3e41c9b199c50a44ff5c8f0a3b5c255ce8 0.600000000000 1469878 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": 1008418, "vin": [ { "gen": { "height": 1008408 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fe7f6a5ebdab08411b36f4cdcff1d3e41c9b199c50a44ff5c8f0a3b5c255ce8" } } ], "extra": [ 1, 139, 193, 7, 174, 72, 62, 200, 12, 154, 239, 29, 23, 117, 47, 236, 151, 75, 145, 99, 100, 49, 203, 160, 44, 89, 85, 91, 33, 215, 220, 1, 247, 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