Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e40583b21a93b0da03b9b867cb5b68d1e284fa819357c3149176bb87aa2237e

Tx prefix hash: a8ecda21e6e6f0eb643f1c8020530ba4a2c004648e1ddae03987b247fbc9fa83
Tx public key: 7f5ffec5cbed3e7616049b8a3561ef759089af4e42e9ae6f908d056fb2c57269
Timestamp: 1747373278 Timestamp [UCT]: 2025-05-16 05:27:58 Age [y:d:h:m:s]: 00:186:03:51:06
Block: 1283954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130760 RingCT/type: yes/0
Extra: 017f5ffec5cbed3e7616049b8a3561ef759089af4e42e9ae6f908d056fb2c572690211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3585634b37d07e398dc5fb461bdf3083438df315eabdb9db1658f221820c3280 0.600000000000 1771389 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": 1283964, "vin": [ { "gen": { "height": 1283954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3585634b37d07e398dc5fb461bdf3083438df315eabdb9db1658f221820c3280" } } ], "extra": [ 1, 127, 95, 254, 197, 203, 237, 62, 118, 22, 4, 155, 138, 53, 97, 239, 117, 144, 137, 175, 78, 66, 233, 174, 111, 144, 141, 5, 111, 178, 197, 114, 105, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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