Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33c852e35a41d04a24b4df6d72c04cf8a276d27f506f7f66670b503849a239b0

Tx prefix hash: 26ad89d9b3c58a395f77e3fc7bba16fcbb029b5519923eaed80f7b7b1cd3914e
Tx public key: fdfe626d13e101aa6d7ab215aeb134d750ac9e37f3d467c344faf1bb0f52110b
Timestamp: 1761378496 Timestamp [UCT]: 2025-10-25 07:48:16 Age [y:d:h:m:s]: 00:023:17:29:39
Block: 1397500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16972 RingCT/type: yes/0
Extra: 01fdfe626d13e101aa6d7ab215aeb134d750ac9e37f3d467c344faf1bb0f52110b021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76a77eb1bd94b0bcbe46c91f14183f2819d764652f577b9171ccfc6c35d2133a 0.600000000000 1885791 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": 1397510, "vin": [ { "gen": { "height": 1397500 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76a77eb1bd94b0bcbe46c91f14183f2819d764652f577b9171ccfc6c35d2133a" } } ], "extra": [ 1, 253, 254, 98, 109, 19, 225, 1, 170, 109, 122, 178, 21, 174, 177, 52, 215, 80, 172, 158, 55, 243, 212, 103, 195, 68, 250, 241, 187, 15, 82, 17, 11, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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