Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 767539b6b0b4971407e18b418f3db5e7433abdd81835ee82745ece884bbb4c61

Tx prefix hash: a8dddc466ebcef8baf52c50976eb98d08a3cc9026ba81a5a3411acb6eab200dc
Tx public key: 20f5996978728d14a766f3bb9dcd987e84df277aa614dff1d31710d85ca0f1e1
Timestamp: 1751662602 Timestamp [UCT]: 2025-07-04 20:56:42 Age [y:d:h:m:s]: 00:133:03:09:00
Block: 1318844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93445 RingCT/type: yes/0
Extra: 0120f5996978728d14a766f3bb9dcd987e84df277aa614dff1d31710d85ca0f1e102110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0ee57b5916b73c937890daa1736a39d3132e344dcc4eeae40c6f24b8e4199ce 0.600000000000 1806531 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": 1318854, "vin": [ { "gen": { "height": 1318844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0ee57b5916b73c937890daa1736a39d3132e344dcc4eeae40c6f24b8e4199ce" } } ], "extra": [ 1, 32, 245, 153, 105, 120, 114, 141, 20, 167, 102, 243, 187, 157, 205, 152, 126, 132, 223, 39, 122, 166, 20, 223, 241, 211, 23, 16, 216, 92, 160, 241, 225, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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