Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29dd773a046c4816d512459f418d3733d15c6582e94e86df7b19d88d576153ca

Tx prefix hash: 235be45a2b19991dfd6bbde751ff791db75b2d303df844a3de4123b80f828fa2
Tx public key: dc6293622e9fa7c5b92c03a50122a533f3c35b8f822e9acd689d615c31a31a6c
Timestamp: 1709901376 Timestamp [UCT]: 2024-03-08 12:36:16 Age [y:d:h:m:s]: 01:257:23:27:09
Block: 973848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443086 RingCT/type: yes/0
Extra: 01dc6293622e9fa7c5b92c03a50122a533f3c35b8f822e9acd689d615c31a31a6c02110000000b52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 857e2c439160c77b6517cb22e1bdb5458ce7cb1def46824c0ee7a0bde3cf3d7d 0.600000000000 1433789 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": 973858, "vin": [ { "gen": { "height": 973848 } } ], "vout": [ { "amount": 600000000, "target": { "key": "857e2c439160c77b6517cb22e1bdb5458ce7cb1def46824c0ee7a0bde3cf3d7d" } } ], "extra": [ 1, 220, 98, 147, 98, 46, 159, 167, 197, 185, 44, 3, 165, 1, 34, 165, 51, 243, 195, 91, 143, 130, 46, 154, 205, 104, 157, 97, 92, 49, 163, 26, 108, 2, 17, 0, 0, 0, 11, 82, 212, 126, 148, 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