Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e16916b2da8877b3ded34ca4813ddb12d65a960aa191cd332f9d3ffbe1eb2ad2

Tx prefix hash: 62209757dbb29f46ff8b5e6c07c92915bacf95e2d9b4c679462a53e69e3a8cef
Tx public key: 2ca168242dcee10d28a2b3f1fefb7dc3370eb83e6212a4e786f4e8a1223ad61f
Timestamp: 1582969886 Timestamp [UCT]: 2020-02-29 09:51:26 Age [y:d:h:m:s]: 04:302:22:40:42
Block: 73900 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1110272 RingCT/type: yes/0
Extra: 012ca168242dcee10d28a2b3f1fefb7dc3370eb83e6212a4e786f4e8a1223ad61f02110000001bc71d3ff9000000000000000000

1 output(s) for total of 349.252417969000 dcy

stealth address amount amount idx
00: 08c43d2cb29b641e295d723331ed012bec9c9a3689fc544230b9feaf6c6e27d5 349.252417969000 136556 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": 73910, "vin": [ { "gen": { "height": 73900 } } ], "vout": [ { "amount": 349252417969, "target": { "key": "08c43d2cb29b641e295d723331ed012bec9c9a3689fc544230b9feaf6c6e27d5" } } ], "extra": [ 1, 44, 161, 104, 36, 45, 206, 225, 13, 40, 162, 179, 241, 254, 251, 125, 195, 55, 14, 184, 62, 98, 18, 164, 231, 134, 244, 232, 161, 34, 58, 214, 31, 2, 17, 0, 0, 0, 27, 199, 29, 63, 249, 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