← previous blocknext block →recent activity
Analyzing
Block #106,100,951
10 transactions · 9 stateful · 2026-09-19 06:05:06 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,100,951 · 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
1w02w03w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3d7b0d3f…a725
0x34b655…2a6f
4 touches
1 conflict
0x58135fb2…9f23
0x34b655…2a6f
4 touches
1 conflict
0x8adc194e…b527
0x754704…b603
4 touches
1 conflict
0xc7e70be2…b0c3
0x754704…b603
4 touches
1 conflict
0xf371c34e…e4ac
0x754704…b603
4 touches
1 conflict
0x16586475…53db
0x99c7a7…8bf0
4 touches
1 conflict
0x85c2666e…5acf
0x99c7a7…8bf0
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
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 0x3d7b0d3ffe…38a725
Audit this contract →
← previous block·next block →recent activity