← previous blocknext block →recent activity
Analyzing
Block #108,103,398
13 transactions · 13 stateful · 2026-09-26 06:07:15 UTC
Parallelism
62/100
Blocked
46%
Avg conflicts / tx
1.15
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,103,398 · 13 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
1w02w13w04w16w09w110w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5dc501b…831c
0x34b655…2a6f
10 touches
10 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x38a06385…ed6a
0x34b655…2a6f
7 touches
6 conflicts
0xd739490d…821e
0x34b655…2a6f
6 touches
3 conflicts
0x26f84fa9…d378
0x34b655…2a6f
5 touches
3 conflicts
0x5969523e…5191
0x34b655…2a6f
4 touches
1 conflict
0x5ad5e6de…e7ad
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
10 conflicts on slot 0xf5dc501bf7…74831c
Audit this contract →
← previous block·next block →recent activity