Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01ec54b2592a00c62ea4dc3af990ba61a3c8b2051fde858bb923739e038727a5

Tx prefix hash: e4c580c269cc83b7a29a3d21767ed80e46100347a3e2a903d7c9770c8a879a04
Tx public key: f8a270019ea6caf4005eb1a87748d53d6954bc40c6a4fab21a41c73592db4a83
Timestamp: 1708236930 Timestamp [UCT]: 2024-02-18 06:15:30 Age [y:d:h:m:s]: 00:269:07:18:43
Block: 960032 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192821 RingCT/type: yes/0
Extra: 01f8a270019ea6caf4005eb1a87748d53d6954bc40c6a4fab21a41c73592db4a8302110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec24acd6bd08c3352870ba0e6d8ce081985d6e346392a62677d9b6dc31748bdc 0.600000000000 1419591 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": 960042, "vin": [ { "gen": { "height": 960032 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec24acd6bd08c3352870ba0e6d8ce081985d6e346392a62677d9b6dc31748bdc" } } ], "extra": [ 1, 248, 162, 112, 1, 158, 166, 202, 244, 0, 94, 177, 168, 119, 72, 213, 61, 105, 84, 188, 64, 198, 164, 250, 178, 26, 65, 199, 53, 146, 219, 74, 131, 2, 17, 0, 0, 0, 3, 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