← previous blocknext block →recent activity
Analyzing
Block #93,338,364
8 transactions · 7 stateful · 2026-08-05 11:44:57 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,338,364 · 8 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3244ff5…7cc1
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x0fb9e50c…1a35
0x34b655…2a6f
4 touches
1 conflict
0x00ddbbf2…4588
0x34b655…2a6f
2 touches
0 conflicts
0x02693e83…54be
0x34b655…2a6f
2 touches
0 conflicts
0x051fdaf9…d512
0x34b655…2a6f
2 touches
0 conflicts
0x0b00852e…b20b
0x34b655…2a6f
2 touches
0 conflicts
0x0c57679c…99c9
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 0xa3244ff56d…bc7cc1
Audit this contract →
← previous block·next block →recent activity