Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a94d144b69b4e19fa9a6cc15949a3cf884ce166a156f5881b600b5e3d98005dc

Tx prefix hash: 5d812e3e8380f6ccb5b21686e1a3b962b3a0a012c9e05664e8fddf581b4ba886
Tx public key: 705f4505da86de86c2ff37f1b40cd8870d64e8cbedd981124f01c982ea102d59
Timestamp: 1723486408 Timestamp [UCT]: 2024-08-12 18:13:28 Age [y:d:h:m:s]: 00:216:18:02:58
Block: 1086458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154807 RingCT/type: yes/0
Extra: 01705f4505da86de86c2ff37f1b40cd8870d64e8cbedd981124f01c982ea102d59021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eac3d99e28f47e12d646baacb1468cabf37ce2c00a9d59fa62668c43d1b723a4 0.600000000000 1561055 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": 1086468, "vin": [ { "gen": { "height": 1086458 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eac3d99e28f47e12d646baacb1468cabf37ce2c00a9d59fa62668c43d1b723a4" } } ], "extra": [ 1, 112, 95, 69, 5, 218, 134, 222, 134, 194, 255, 55, 241, 180, 12, 216, 135, 13, 100, 232, 203, 237, 217, 129, 18, 79, 1, 201, 130, 234, 16, 45, 89, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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