Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f919c61bcae6f9bf257183a950f87e96f1b6e93a2569c77ca1a4f7ac1104efd3

Tx prefix hash: bd6ec8775c341d33a73ea11238ebccf80d422072557ad4fefdfd2f50a2e87a00
Tx public key: 311aaaf8fad73f4d153d6975c74f23293f1196a0f89c9227c5c16e2012c93c0e
Timestamp: 1583856982 Timestamp [UCT]: 2020-03-10 16:16:22 Age [y:d:h:m:s]: 05:038:08:51:35
Block: 79957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1183133 RingCT/type: yes/0
Extra: 01311aaaf8fad73f4d153d6975c74f23293f1196a0f89c9227c5c16e2012c93c0e0211000000023b1b9791000000000000000000

1 output(s) for total of 333.480203066000 dcy

stealth address amount amount idx
00: a2fc122bf685644e87dd769b696b59ac8fbd1383baa9ef4d9dc1f667d837415d 333.480203066000 146293 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": 79967, "vin": [ { "gen": { "height": 79957 } } ], "vout": [ { "amount": 333480203066, "target": { "key": "a2fc122bf685644e87dd769b696b59ac8fbd1383baa9ef4d9dc1f667d837415d" } } ], "extra": [ 1, 49, 26, 170, 248, 250, 215, 63, 77, 21, 61, 105, 117, 199, 79, 35, 41, 63, 17, 150, 160, 248, 156, 146, 39, 197, 193, 110, 32, 18, 201, 60, 14, 2, 17, 0, 0, 0, 2, 59, 27, 151, 145, 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