← previous blocknext block →recent activity
Analyzing
Block #108,516,837
13 transactions · 12 stateful · 2026-09-27 16:48:04 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,516,837 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w18w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfdf1a05b…1e18
0x34b655…2a6f
4 touches
1 conflict
0xb7268296…4f52
0x34b655…2a6f
4 touches
1 conflict
0xbd590df7…9891
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0xe763a93c…e90b
0x34b655…2a6f
4 touches
1 conflict
0xf8b7e65f…2816
0x34b655…2a6f
4 touches
1 conflict
0x05c53b92…de27
0x34b655…2a6f
4 touches
1 conflict
0x114dfee0…297e
0x34b655…2a6f
4 touches
1 conflict
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 0xfdf1a05ba4…401e18
Audit this contract →
← previous block·next block →recent activity