Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd93610bb8f18832f2afee66d640e6b3a05a3d8acb8b0abb2d79507201c021c9

Tx prefix hash: c91b443a04bbb4e9e08fcdee127f272523fcc1f76bc0a20bc08a1c51a8a2367e
Tx public key: 778ed2d41834f2e407830c09b1b1124ac55008e8cd4fbd71ffdf1d10b358d484
Timestamp: 1755710324 Timestamp [UCT]: 2025-08-20 17:18:44 Age [y:d:h:m:s]: 00:046:05:40:11
Block: 1350724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32880 RingCT/type: yes/0
Extra: 01778ed2d41834f2e407830c09b1b1124ac55008e8cd4fbd71ffdf1d10b358d484021100000006ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c41dd9f16d6b817bfb0aaf88ec913affcf7513de8911efae30d5f154c733b0fa 0.600000000000 1838671 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": 1350734, "vin": [ { "gen": { "height": 1350724 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c41dd9f16d6b817bfb0aaf88ec913affcf7513de8911efae30d5f154c733b0fa" } } ], "extra": [ 1, 119, 142, 210, 212, 24, 52, 242, 228, 7, 131, 12, 9, 177, 177, 18, 74, 197, 80, 8, 232, 205, 79, 189, 113, 255, 223, 29, 16, 179, 88, 212, 132, 2, 17, 0, 0, 0, 6, 173, 121, 72, 208, 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