← previous blocknext block →recent activity
Analyzing
Block #108,605,086
23 transactions · 23 stateful · 2026-09-28 00:12:28 UTC
Parallelism
65/100
Blocked
52%
Avg conflicts / tx
1.61
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,605,086 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w27w38w49w510w613w114w218w219w122w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b780b26…f5ff
0x34b655…2a6f
16 touches
28 conflicts
0x0ddc998e…def8
0x34b655…2a6f
16 touches
28 conflicts
0x16d77246…bac5
0x34b655…2a6f
14 touches
21 conflicts
0x280aaa58…1c52
0x34b655…2a6f
14 touches
21 conflicts
0x309f47c0…e1cf
0x34b655…2a6f
14 touches
21 conflicts
0x3b65c5ca…9f83
0x34b655…2a6f
14 touches
21 conflicts
0x6cc2bd64…4143
0x34b655…2a6f
14 touches
21 conflicts
0x739123da…57f3
0x34b655…2a6f
14 touches
21 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
28 conflicts on slot 0x8b780b2668…85f5ff
Audit this contract →
← previous block·next block →recent activity