← previous blocknext block →recent activity
Analyzing
Block #108,493,954
21 transactions · 20 stateful · 2026-09-27 14:52:51 UTC
Parallelism
81/100
Blocked
20%
Avg conflicts / tx
0.24
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,493,954 · 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
1w05w113w214w316w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19dcf812…44d9
0x34b655…2a6f
6 touches
3 conflicts
0xdac9358f…27ac
0x34b655…2a6f
4 touches
1 conflict
0x1cf4d26f…9415
0x34b655…2a6f
4 touches
1 conflict
0x26b816a2…89a5
0x34b655…2a6f
4 touches
1 conflict
0x31d88d27…7617
0x34b655…2a6f
4 touches
1 conflict
0x7292cf72…77f6
0x34b655…2a6f
4 touches
1 conflict
0x8d5fc820…1750
0x34b655…2a6f
4 touches
1 conflict
0xc4c059d8…185d
0x34b655…2a6f
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 0x19dcf812b9…df44d9
Audit this contract →
← previous block·next block →recent activity