← previous blocknext block →recent activity
Analyzing
Block #106,031,398
15 transactions · 15 stateful · 2026-09-19 00:15:05 UTC
Parallelism
87/100
Blocked
27%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,031,398 · 15 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
1w02w13w04w19w010w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6ca15e14…7be8
0x34b655…2a6f
4 touches
1 conflict
0xc7e70be2…b0c3
0x754704…b603
4 touches
1 conflict
0xf371c34e…e4ac
0x754704…b603
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x7d7eda01…b1d1
0x99c7a7…8bf0
4 touches
1 conflict
0xf4078e26…6d12
0xd32edf…ff58
3 touches
1 conflict
0x09d04cc1…bbdb
0x8f415d…5241
3 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
1 conflict on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity