Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e03ad0f729367739700bd722be606b5c5a127d1fdb7e3571a9c40663f6da699e

Tx prefix hash: 8248526c878f550710b741aa215faf7e8180f70ea2e284d505ff07c9768edbb8
Tx public key: 9fef11547f28080af8f0bb814b0da4331c39a955513dd6325d5f9e2882a6ef97
Timestamp: 1700672771 Timestamp [UCT]: 2023-11-22 17:06:11 Age [y:d:h:m:s]: 01:092:23:10:26
Block: 897324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327566 RingCT/type: yes/0
Extra: 019fef11547f28080af8f0bb814b0da4331c39a955513dd6325d5f9e2882a6ef9702110000000775e3f0e9000000000000000000

1 output(s) for total of 0.652819440000 dcy

stealth address amount amount idx
00: 456e2581222c35d7d8262574562046d0e7960d2d9d3043070f579d9f4b24b2a8 0.652819440000 1353699 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": 897334, "vin": [ { "gen": { "height": 897324 } } ], "vout": [ { "amount": 652819440, "target": { "key": "456e2581222c35d7d8262574562046d0e7960d2d9d3043070f579d9f4b24b2a8" } } ], "extra": [ 1, 159, 239, 17, 84, 127, 40, 8, 10, 248, 240, 187, 129, 75, 13, 164, 51, 28, 57, 169, 85, 81, 61, 214, 50, 93, 95, 158, 40, 130, 166, 239, 151, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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