Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d915514b6c5f5981e1547cc5a29a4b3c61e5f7b445f40182c647ae883156e84

Tx prefix hash: bf4e2ae4a07eb0a1fe60870c2f9e2f1453625ee9db1f009b95bbb2a66948115e
Tx public key: 910f82e358cf6b611f46825ed01bcca62509077d574641ee6bc474e13a9e9963
Timestamp: 1703734857 Timestamp [UCT]: 2023-12-28 03:40:57 Age [y:d:h:m:s]: 01:140:10:48:06
Block: 922707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361519 RingCT/type: yes/0
Extra: 01910f82e358cf6b611f46825ed01bcca62509077d574641ee6bc474e13a9e9963021100000006ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35807b67d475681bb628cef22d89cac0661efb262e7e0a27f4f1ba3c5f4af012 0.600000000000 1380411 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": 922717, "vin": [ { "gen": { "height": 922707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35807b67d475681bb628cef22d89cac0661efb262e7e0a27f4f1ba3c5f4af012" } } ], "extra": [ 1, 145, 15, 130, 227, 88, 207, 107, 97, 31, 70, 130, 94, 208, 27, 204, 166, 37, 9, 7, 125, 87, 70, 65, 238, 107, 196, 116, 225, 58, 158, 153, 99, 2, 17, 0, 0, 0, 6, 173, 86, 148, 172, 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