Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1f3d93c5b992b5f085dec3ef03c8ceee82d03a185eab07db39dbf51e1651e9f

Tx prefix hash: eb7e124db57f04fa91068ad02317c58b8e5147e16eb1db149d730e6257591472
Tx public key: 0210864e901e0408a7bfd04ce9c3a4bf058ef7bfa829453369d9c1e555167628
Timestamp: 1675993473 Timestamp [UCT]: 2023-02-10 01:44:33 Age [y:d:h:m:s]: 01:353:22:29:11
Block: 693600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 513678 RingCT/type: yes/0
Extra: 010210864e901e0408a7bfd04ce9c3a4bf058ef7bfa829453369d9c1e5551676280211000000065029cbac000000000000000000

1 output(s) for total of 3.088980705000 dcy

stealth address amount amount idx
00: 5d5a1c87d7f283a02d5cbee9bd39fe2716257a178917782b447c964155f100b3 3.088980705000 1136497 of 0

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": 693610, "vin": [ { "gen": { "height": 693600 } } ], "vout": [ { "amount": 3088980705, "target": { "key": "5d5a1c87d7f283a02d5cbee9bd39fe2716257a178917782b447c964155f100b3" } } ], "extra": [ 1, 2, 16, 134, 78, 144, 30, 4, 8, 167, 191, 208, 76, 233, 195, 164, 191, 5, 142, 247, 191, 168, 41, 69, 51, 105, 217, 193, 229, 85, 22, 118, 40, 2, 17, 0, 0, 0, 6, 80, 41, 203, 172, 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