Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86dc8b4b30e1948579e382a0a2f28a4f220479edf6144c0f95e67a2b8380aac2

Tx prefix hash: 133ab44ae33723b17e591a642f722cd9bd564bd347bad2ceb70385494536dbe1
Tx public key: 40111e421c83c6e9c997e947347f79c9133e0c3955d0840beec8f5ae65c9b760
Timestamp: 1758268929 Timestamp [UCT]: 2025-09-19 08:02:09 Age [y:d:h:m:s]: 00:111:04:41:36
Block: 1371716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79623 RingCT/type: yes/0
Extra: 0140111e421c83c6e9c997e947347f79c9133e0c3955d0840beec8f5ae65c9b760021100000006ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c925ba53d0618bda8e3ad078a70f91851e19c96fcd3191a3faa9d3d10e7e7c9 0.600000000000 1859793 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": 1371726, "vin": [ { "gen": { "height": 1371716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c925ba53d0618bda8e3ad078a70f91851e19c96fcd3191a3faa9d3d10e7e7c9" } } ], "extra": [ 1, 64, 17, 30, 66, 28, 131, 198, 233, 201, 151, 233, 71, 52, 127, 121, 201, 19, 62, 12, 57, 85, 208, 132, 11, 238, 200, 245, 174, 101, 201, 183, 96, 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