Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d54d0cb127a3777a7deaaab97bd4d487a966bfb17cda08ee83772872a0255f40

Tx prefix hash: 6ee1354598339710a902658c592f25477d493ce9f12c8325bd7c70f95643053a
Tx public key: e9b0ae1c41a270211e6b03a39b65dd691f8b9d2e7ad00a8f293588115a2d16be
Timestamp: 1751358033 Timestamp [UCT]: 2025-07-01 08:20:33 Age [y:d:h:m:s]: 00:136:00:31:53
Block: 1316421 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95419 RingCT/type: yes/0
Extra: 01e9b0ae1c41a270211e6b03a39b65dd691f8b9d2e7ad00a8f293588115a2d16be02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 600bad54fe37c82458fae0f793b008da7d6809b98cf075b9ee0bbebf820ab7a9 0.600000000000 1804080 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": 1316431, "vin": [ { "gen": { "height": 1316421 } } ], "vout": [ { "amount": 600000000, "target": { "key": "600bad54fe37c82458fae0f793b008da7d6809b98cf075b9ee0bbebf820ab7a9" } } ], "extra": [ 1, 233, 176, 174, 28, 65, 162, 112, 33, 30, 107, 3, 163, 155, 101, 221, 105, 31, 139, 157, 46, 122, 208, 10, 143, 41, 53, 136, 17, 90, 45, 22, 190, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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