← previous blocknext block →recent activity
Analyzing
Block #108,640,670
25 transactions · 21 stateful · 2026-09-28 03:11:43 UTC
Parallelism
80/100
Blocked
43%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,640,670 · 25 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
1w02w14w05w16w215w016w117w218w319w222w023w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60b8d1a4…3c00
0x34b655…2a6f
6 touches
3 conflicts
0x2029b74e…c206
0x34b655…2a6f
6 touches
3 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x5060cdde…445d
0x34b655…2a6f
4 touches
1 conflict
0x6565e902…fe98
0x34b655…2a6f
4 touches
1 conflict
0x7c3ddfce…2c39
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
3 conflicts on slot 0x60b8d1a48c…2d3c00
Audit this contract →
← previous block·next block →recent activity