← previous blocknext block →recent activity
Analyzing
Block #93,558,744
10 transactions · 10 stateful · 2026-08-06 06:12:53 UTC
Parallelism
80/100
Blocked
30%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,558,744 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd676e291…3ecf
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x1bf8d2af…d140
0x34b655…2a6f
4 touches
1 conflict
0x00210867…83b6
0x34b655…2a6f
2 touches
0 conflicts
0x00cba8ba…84a6
0x34b655…2a6f
2 touches
0 conflicts
0x21dfacd7…d2f6
0x34b655…2a6f
2 touches
0 conflicts
0x40c5d5cc…d164
0x34b655…2a6f
2 touches
0 conflicts
0x4738f4d1…5266
0x34b655…2a6f
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
1 conflict on slot 0xd676e29175…2b3ecf
Audit this contract →
← previous block·next block →recent activity