← previous blocknext block →recent activity
Analyzing
Block #93,843,241
21 transactions · 18 stateful · 2026-08-07 06:03:07 UTC
Parallelism
76/100
Blocked
22%
Avg conflicts / tx
0.19
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,843,241 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xa6b89ebb…a66e
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x03aa8b26…118a
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x4bdf8cd0…11c0
0x34b655…2a6f
4 touches
1 conflict
0xb8727385…d147
0x34b655…2a6f
2 touches
0 conflicts
0xc1a4c088…e828
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 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity