← previous blocknext block →recent activity
Analyzing
Block #106,163,634
12 transactions · 12 stateful · 2026-09-19 11:20:34 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,163,634 · 12 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
1w05w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42b09045…0624
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xc8ed6914…a4bd
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x1ccd2de8…8ee6
0x34b655…2a6f
2 touches
0 conflicts
0x3a9b40f8…d6f5
0x34b655…2a6f
2 touches
0 conflicts
0x67043b0b…97d7
0x34b655…2a6f
2 touches
0 conflicts
0x6942efcb…a509
0x34b655…2a6f
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 0x42b0904507…c00624
Audit this contract →
← previous block·next block →recent activity