Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05f9e478b4030bf74baaddd49c53a164313f2a1b2ccd47ccd7bf4edf29ed38ea

Tx prefix hash: adbb9d7f52cea57a80928e4f7531ea8be4f1df210866e32d23b43a171620f807
Tx public key: 6a04e669d0b14c653d50c045d4a4a5ded6268b81bf481448b984c8e252754e9a
Timestamp: 1761559043 Timestamp [UCT]: 2025-10-27 09:57:23 Age [y:d:h:m:s]: 00:057:00:41:44
Block: 1398996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40801 RingCT/type: yes/0
Extra: 016a04e669d0b14c653d50c045d4a4a5ded6268b81bf481448b984c8e252754e9a0211000000015dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03b303c57972d693f21011430ee6bc247cf1e696c3e6ae7ebf6457841a0438ec 0.600000000000 1887299 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": 1399006, "vin": [ { "gen": { "height": 1398996 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03b303c57972d693f21011430ee6bc247cf1e696c3e6ae7ebf6457841a0438ec" } } ], "extra": [ 1, 106, 4, 230, 105, 208, 177, 76, 101, 61, 80, 192, 69, 212, 164, 165, 222, 214, 38, 139, 129, 191, 72, 20, 72, 185, 132, 200, 226, 82, 117, 78, 154, 2, 17, 0, 0, 0, 1, 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