← previous blocknext block →recent activity
Analyzing
Block #108,009,696
18 transactions · 18 stateful · 2026-09-25 22:15:45 UTC
Parallelism
89/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,009,696 · 18 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
2w03w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c1cc07a…b400
0x34b655…2a6f
4 touches
1 conflict
0x908b3417…88d2
0x34b655…2a6f
4 touches
1 conflict
0xaf7f13f9…a2c9
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x3f2880e3…37ec
0x34b655…2a6f
4 touches
1 conflict
0x19d946cd…e72e
0x065c9d…c394
2 touches
0 conflicts
0x3666f25e…5889
0x065c9d…c394
2 touches
0 conflicts
0xcacaa623…d09a
0x065c9d…c394
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 0x5c1cc07aeb…ebb400
Audit this contract →
← previous block·next block →recent activity