← previous blocknext block →recent activity
Analyzing
Block #106,034,481
10 transactions · 10 stateful · 2026-09-19 00:30:36 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,034,481 · 10 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
1w02w14w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xfc224d25…b474
0x34b655…2a6f
4 touches
1 conflict
0x6658fa82…4017
0x754704…b603
4 touches
1 conflict
0xc7e70be2…b0c3
0x754704…b603
4 touches
1 conflict
0xf371c34e…e4ac
0x754704…b603
4 touches
1 conflict
0x11db128b…1153
0x34b655…2a6f
2 touches
0 conflicts
0x1832b47f…040d
0x34b655…2a6f
2 touches
0 conflicts
0x283c5d96…ffc2
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 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity