← previous blocknext block →recent activity
Analyzing
Block #108,447,994
10 transactions · 10 stateful · 2026-09-27 11:01:30 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,447,994 · 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2dfcd43…4b17
0x34b655…2a6f
4 touches
1 conflict
0x132b9de1…183b
0x34b655…2a6f
4 touches
1 conflict
0x518b8dce…6d60
0x34b655…2a6f
4 touches
1 conflict
0x68971f58…8196
0x34b655…2a6f
4 touches
1 conflict
0x1f84ce8a…5acc
0x34b655…2a6f
4 touches
1 conflict
0x03f699e7…537e
0x34b655…2a6f
2 touches
0 conflicts
0x1b92ad61…dd91
0x34b655…2a6f
2 touches
0 conflicts
0x1fd413e8…cf35
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 0xf2dfcd439a…4d4b17
Audit this contract →
← previous block·next block →recent activity