← previous blocknext block →recent activity
Analyzing
Block #108,611,631
38 transactions · 35 stateful · 2026-09-28 00:45:26 UTC
Parallelism
55/100
Blocked
69%
Avg conflicts / tx
2.79
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #108,611,631 · 38 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w27w38w49w510w611w712w816w520w922w1023w1124w1227w128w129w130w235w1436w1537w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
24 touches
66 conflicts
0x098936f4…836d
0x34b655…2a6f
16 touches
28 conflicts
0x0d54fa3e…3b3c
0x34b655…2a6f
16 touches
28 conflicts
0x16d77246…bac5
0x34b655…2a6f
16 touches
28 conflicts
0x22badbc6…4c24
0x34b655…2a6f
16 touches
28 conflicts
0x280aaa58…1c52
0x34b655…2a6f
16 touches
28 conflicts
0x309f47c0…e1cf
0x34b655…2a6f
16 touches
28 conflicts
0x3b65c5ca…9f83
0x34b655…2a6f
16 touches
28 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
66 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity