Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e9775d6d518cdf1636f8d6131310848d017120f8b5557ff462ffe3169ebfbe8

Tx prefix hash: ec7f44ba22f06501b1ba011686894ee085da392008b1a7c9909d250c78b05de5
Tx public key: 50abfb1cb694432421db61f80b38723a8045846bd65e6c74f3f4771dca86d946
Timestamp: 1721849930 Timestamp [UCT]: 2024-07-24 19:38:50 Age [y:d:h:m:s]: 00:122:12:12:29
Block: 1072885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87664 RingCT/type: yes/0
Extra: 0150abfb1cb694432421db61f80b38723a8045846bd65e6c74f3f4771dca86d946021100000010e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c3fcdb50ca88575290323f4c2aa9c9e69b59c3f257ee7ddf0fb8e102e7d7eac 0.600000000000 1545382 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": 1072895, "vin": [ { "gen": { "height": 1072885 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c3fcdb50ca88575290323f4c2aa9c9e69b59c3f257ee7ddf0fb8e102e7d7eac" } } ], "extra": [ 1, 80, 171, 251, 28, 182, 148, 67, 36, 33, 219, 97, 248, 11, 56, 114, 58, 128, 69, 132, 107, 214, 94, 108, 116, 243, 244, 119, 29, 202, 134, 217, 70, 2, 17, 0, 0, 0, 16, 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