Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0960a935312fe978e90c8529607fd977467d9e9547596bfce0d355a89c1e00d5

Tx prefix hash: 2f46539c3c86bb9754895d3ba26a0a3b40a64fcdc058ce2cf8a458bdbb343901
Tx public key: e1b0453f824a238bc669a4c0bc3465555d298be8809a4e82a436a2b72bbdcdf9
Timestamp: 1754566795 Timestamp [UCT]: 2025-08-07 11:39:55 Age [y:d:h:m:s]: 00:105:10:06:31
Block: 1342108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74403 RingCT/type: yes/0
Extra: 01e1b0453f824a238bc669a4c0bc3465555d298be8809a4e82a436a2b72bbdcdf902110000000cb2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: feee8bfa8855711c80224b9171b4a1f6d0e72a669d62f46dcb8f976245f63957 0.600000000000 1829937 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": 1342118, "vin": [ { "gen": { "height": 1342108 } } ], "vout": [ { "amount": 600000000, "target": { "key": "feee8bfa8855711c80224b9171b4a1f6d0e72a669d62f46dcb8f976245f63957" } } ], "extra": [ 1, 225, 176, 69, 63, 130, 74, 35, 139, 198, 105, 164, 192, 188, 52, 101, 85, 93, 41, 139, 232, 128, 154, 78, 130, 164, 54, 162, 183, 43, 189, 205, 249, 2, 17, 0, 0, 0, 12, 178, 247, 132, 196, 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