Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7482ed7c3aec03fd53fa01e0c2e85ddaa13e90f0e9113fbd7bdd959e24f7c13

Tx prefix hash: 95f8f0a606d905fb8e11ae359ffebfab6c39e02204c6fe6ba585797692feacbc
Tx public key: 58a4269446655c14a51d74822eb0390af5d099ab70c29638c5b37f8dcab41a2f
Timestamp: 1759679317 Timestamp [UCT]: 2025-10-05 15:48:37 Age [y:d:h:m:s]: 00:079:08:26:24
Block: 1383393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56814 RingCT/type: yes/0
Extra: 0158a4269446655c14a51d74822eb0390af5d099ab70c29638c5b37f8dcab41a2f021100000001a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e4549860e9addf26be452053dc6d06820c41b6d738bcee8801a0f5f7e498f69 0.600000000000 1871538 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": 1383403, "vin": [ { "gen": { "height": 1383393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e4549860e9addf26be452053dc6d06820c41b6d738bcee8801a0f5f7e498f69" } } ], "extra": [ 1, 88, 164, 38, 148, 70, 101, 92, 20, 165, 29, 116, 130, 46, 176, 57, 10, 245, 208, 153, 171, 112, 194, 150, 56, 197, 179, 127, 141, 202, 180, 26, 47, 2, 17, 0, 0, 0, 1, 165, 220, 205, 121, 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