← previous blocknext block →recent activity
Analyzing
Block #108,286,064
21 transactions · 18 stateful · 2026-09-26 21:26:34 UTC
Parallelism
81/100
Blocked
44%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,286,064 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w08w19w210w116w117w219w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c1cc07a…b400
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x2768f3e8…fe70
0x34b655…2a6f
4 touches
1 conflict
0x3f7c27ed…f757
0x34b655…2a6f
4 touches
1 conflict
0x42744667…0b8a
0x34b655…2a6f
4 touches
1 conflict
0x9b6ca232…c9ff
0xc8689a…ee79
4 touches
1 conflict
0x00000000…0002
0x125f12…a50b
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 0x5c1cc07aeb…ebb400
Audit this contract →
← previous block·next block →recent activity