← previous blocknext block →recent activity
Analyzing
Block #108,402,099
13 transactions · 13 stateful · 2026-09-27 07:10:29 UTC
Parallelism
85/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,402,099 · 13 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
6w07w08w19w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc1a0b28e…f81b
0x34b655…2a6f
4 touches
1 conflict
0x03f699e7…537e
0x34b655…2a6f
4 touches
1 conflict
0x235bbb77…89ea
0x34b655…2a6f
4 touches
1 conflict
0x3324275f…6ef4
0x34b655…2a6f
4 touches
1 conflict
0x3a85dbec…e24d
0x34b655…2a6f
4 touches
1 conflict
0x660b6e4f…3d72
0x34b655…2a6f
4 touches
1 conflict
0x9674d680…261b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
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 0xc1a0b28e03…eef81b
Audit this contract →
← previous block·next block →recent activity