Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d35f698ac4f3964bc86cc4399a89e605fb6a656517277c377bd53bcb42f9740c

Tx prefix hash: 556f00d810b6b7cc5a00fb3d1abf4e847a97a02e13b269ab60069facc97d75d4
Tx public key: c91f270efb3a92697618c0ce862c926e49fceeaef4c1d3fc9bb35279c9f8a8d8
Timestamp: 1733712553 Timestamp [UCT]: 2024-12-09 02:49:13 Age [y:d:h:m:s]: 00:103:06:24:44
Block: 1171143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73596 RingCT/type: yes/0
Extra: 01c91f270efb3a92697618c0ce862c926e49fceeaef4c1d3fc9bb35279c9f8a8d8021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f52f316aa2d370b70e4edff0ae38b37c45d05d4aa782cc3d6ae2181e89556986 0.600000000000 1656880 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": 1171153, "vin": [ { "gen": { "height": 1171143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f52f316aa2d370b70e4edff0ae38b37c45d05d4aa782cc3d6ae2181e89556986" } } ], "extra": [ 1, 201, 31, 39, 14, 251, 58, 146, 105, 118, 24, 192, 206, 134, 44, 146, 110, 73, 252, 238, 174, 244, 193, 211, 252, 155, 179, 82, 121, 201, 248, 168, 216, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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