Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 544114f583431825b2d20c4d7ddf2487d1f3250b6ac74ff47a470d2cd9342b9c

Tx prefix hash: 97dc4747bed625df39b18167ad064a86fb63ed6165e9f6ecaa38cc1317ad614b
Tx public key: 1aff5d59a7bffaf96e3aa2b5a991b20ac8afbb656c6a42f8fdd1c1fb7d6e89a3
Timestamp: 1704212186 Timestamp [UCT]: 2024-01-02 16:16:26 Age [y:d:h:m:s]: 01:095:02:36:57
Block: 926657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329076 RingCT/type: yes/0
Extra: 011aff5d59a7bffaf96e3aa2b5a991b20ac8afbb656c6a42f8fdd1c1fb7d6e89a30211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c663de20990b7b49711bd8f562599fff689153c4d9dc1e4ef4826b666aa6827 0.600000000000 1384453 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": 926667, "vin": [ { "gen": { "height": 926657 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c663de20990b7b49711bd8f562599fff689153c4d9dc1e4ef4826b666aa6827" } } ], "extra": [ 1, 26, 255, 93, 89, 167, 191, 250, 249, 110, 58, 162, 181, 169, 145, 178, 10, 200, 175, 187, 101, 108, 106, 66, 248, 253, 209, 193, 251, 125, 110, 137, 163, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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