Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae6705eae7551fbbe249d24fe9d3f3cf27c2aaa2da223e6074ef70bb0266fd15

Tx prefix hash: 21d8c6001e5e273f71e0cd2a277650f47114b7ddea66ed6943b25189df20736a
Tx public key: d1c2de5fb20ad782229c0b4f5da9d3373705fd495d5c6610120494daa4b06fd6
Timestamp: 1634984505 Timestamp [UCT]: 2021-10-23 10:21:45 Age [y:d:h:m:s]: 03:013:14:44:40
Block: 358757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 787986 RingCT/type: yes/0
Extra: 01d1c2de5fb20ad782229c0b4f5da9d3373705fd495d5c6610120494daa4b06fd6021100000005a272b9cb000000000000000000

1 output(s) for total of 39.745644401000 dcy

stealth address amount amount idx
00: e6a05beeaabe3f0f73da220e1f6c58b3ebb7123d974a5b143b920efcb271d7a6 39.745644401000 730852 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": 358767, "vin": [ { "gen": { "height": 358757 } } ], "vout": [ { "amount": 39745644401, "target": { "key": "e6a05beeaabe3f0f73da220e1f6c58b3ebb7123d974a5b143b920efcb271d7a6" } } ], "extra": [ 1, 209, 194, 222, 95, 178, 10, 215, 130, 34, 156, 11, 79, 93, 169, 211, 55, 55, 5, 253, 73, 93, 92, 102, 16, 18, 4, 148, 218, 164, 176, 111, 214, 2, 17, 0, 0, 0, 5, 162, 114, 185, 203, 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