← previous blocknext block →recent activity
Analyzing
Block #106,099,878
21 transactions · 19 stateful · 2026-09-19 05:59:42 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,099,878 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w09w011w112w213w314w115w416w017w118w519w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09a6fd75…4ac3
0x34b655…2a6f
10 touches
10 conflicts
0x063d8932…afa5
0x34b655…2a6f
8 touches
6 conflicts
0xcd5c0ecb…4b5f
0x34b655…2a6f
8 touches
6 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
6 touches
3 conflicts
0xdc90bed5…58a9
0x34b655…2a6f
6 touches
3 conflicts
0x70986451…c6bd
0x34b655…2a6f
4 touches
1 conflict
0x7fec4dea…6005
0x34b655…2a6f
4 touches
1 conflict
0x85eb1316…bb9e
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
10 conflicts on slot 0x09a6fd755b…eb4ac3
Audit this contract →
← previous block·next block →recent activity