Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0eafc9e7a16c0d0281e19c285151cd2175a26779d3facbc91a9af7d4378c0589

Tx prefix hash: f97fbaaee03c5709a29f9bfa7f745b7a5a1f7a31dc3d437d8a9dae79411987ab
Tx public key: 05f42cea7179beefdc2a2652c89395c6ae340f4adad1af19ba0e7128f75ee6f2
Timestamp: 1739142696 Timestamp [UCT]: 2025-02-09 23:11:36 Age [y:d:h:m:s]: 00:327:21:24:56
Block: 1215823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232178 RingCT/type: yes/0
Extra: 0105f42cea7179beefdc2a2652c89395c6ae340f4adad1af19ba0e7128f75ee6f2021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f4cd723083bd9e9d2c3323eb8cea71a628516d160233502fcd2519ba5e2fb9a 0.600000000000 1702622 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": 1215833, "vin": [ { "gen": { "height": 1215823 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f4cd723083bd9e9d2c3323eb8cea71a628516d160233502fcd2519ba5e2fb9a" } } ], "extra": [ 1, 5, 244, 44, 234, 113, 121, 190, 239, 220, 42, 38, 82, 200, 147, 149, 198, 174, 52, 15, 74, 218, 209, 175, 25, 186, 14, 113, 40, 247, 94, 230, 242, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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