Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b6f0b8ba95b6716e86f9e1870ff6ee32ca173ed6e9d7a5e856229e48a02d350

Tx prefix hash: c6337073851a67600e528a282332334c23f6d4b69c1cb0732e679ca0ef511fc9
Tx public key: 6fbb091a0229b97dc84b18b3fe104b3e1e811e1cbb49a4211521db970f975680
Timestamp: 1761509366 Timestamp [UCT]: 2025-10-26 20:09:26 Age [y:d:h:m:s]: 00:057:13:37:33
Block: 1398584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41199 RingCT/type: yes/0
Extra: 016fbb091a0229b97dc84b18b3fe104b3e1e811e1cbb49a4211521db970f975680021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b230e742b1d796e5e81afa26c532ba1aa7c06d4bda7b90eb1a10458179eb957 0.600000000000 1886885 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": 1398594, "vin": [ { "gen": { "height": 1398584 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b230e742b1d796e5e81afa26c532ba1aa7c06d4bda7b90eb1a10458179eb957" } } ], "extra": [ 1, 111, 187, 9, 26, 2, 41, 185, 125, 200, 75, 24, 179, 254, 16, 75, 62, 30, 129, 30, 28, 187, 73, 164, 33, 21, 33, 219, 151, 15, 151, 86, 128, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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