Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6720d8019bdad94fa1101614106653b0f5a0b6cc8e6b5f7b9ec965d7fd79fbf

Tx prefix hash: 44cd0f8b0ba5ef8866ba0c5d31c3e79c6b66a21567aa919cd554c11e7b897e01
Tx public key: ebef2d833fabd4f689a1417a286c1bfd83a68dc42d5b53393a2cf6dc2114cb7f
Timestamp: 1764109267 Timestamp [UCT]: 2025-11-25 22:21:07 Age [y:d:h:m:s]: 00:000:16:07:00
Block: 1420122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 471 RingCT/type: yes/0
Extra: 01ebef2d833fabd4f689a1417a286c1bfd83a68dc42d5b53393a2cf6dc2114cb7f021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1087d63a61f7f98b09aca1d0ce5598d2dcace778eae2b734c5d7b5eca51c8891 0.600000000000 1908663 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": 1420132, "vin": [ { "gen": { "height": 1420122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1087d63a61f7f98b09aca1d0ce5598d2dcace778eae2b734c5d7b5eca51c8891" } } ], "extra": [ 1, 235, 239, 45, 131, 63, 171, 212, 246, 137, 161, 65, 122, 40, 108, 27, 253, 131, 166, 141, 196, 45, 91, 83, 57, 58, 44, 246, 220, 33, 20, 203, 127, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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