← previous blocknext block →recent activity
Analyzing
Block #106,342,591
25 transactions · 25 stateful · 2026-09-20 02:21:15 UTC
Parallelism
92/100
Blocked
12%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,342,591 · 25 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
1w06w09w010w113w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ba10aad…9bc5
0x34b655…2a6f
4 touches
1 conflict
0x662e354e…e306
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x1adde00d…ed31
0xa6afd3…d132
4 touches
1 conflict
0x3a3e7727…36c5
0x34ae4d…3fc5
2 touches
0 conflicts
0x62811193…1867
0x34ae4d…3fc5
2 touches
0 conflicts
0x62811193…186c
0x34ae4d…3fc5
2 touches
0 conflicts
0xd671bc34…553c
0x34ae4d…3fc5
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 0x9ba10aada6…3c9bc5
Audit this contract →
← previous block·next block →recent activity