Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 264553f4b91e1ebc05377134f0a401aea058476ff92e334e91cc0ebd07b9cfd3

Tx prefix hash: f4fb92302730b8dcf86fb88dbba9e463e42b755e77bdd661e60b8e56bb087a57
Tx public key: 7a7324fe327bf4183326d35a5cbc22a5e05e49f76319fb2bc3710e5aed808a2a
Timestamp: 1761828856 Timestamp [UCT]: 2025-10-30 12:54:16 Age [y:d:h:m:s]: 00:008:22:28:08
Block: 1401225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6383 RingCT/type: yes/0
Extra: 017a7324fe327bf4183326d35a5cbc22a5e05e49f76319fb2bc3710e5aed808a2a0211000000085dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67657b76427769df7550855aaed562b0cb9e61109c1f463a23b3f8097a9d7216 0.600000000000 1889544 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": 1401235, "vin": [ { "gen": { "height": 1401225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67657b76427769df7550855aaed562b0cb9e61109c1f463a23b3f8097a9d7216" } } ], "extra": [ 1, 122, 115, 36, 254, 50, 123, 244, 24, 51, 38, 211, 90, 92, 188, 34, 165, 224, 94, 73, 247, 99, 25, 251, 43, 195, 113, 14, 90, 237, 128, 138, 42, 2, 17, 0, 0, 0, 8, 93, 251, 190, 42, 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