← previous blocknext block →recent activity
Analyzing
Block #106,906,912
16 transactions · 13 stateful · 2026-09-22 01:42:31 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,906,912 · 16 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
1w02w13w04w05w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7fc8f46e…0f75
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe4a10d60…841b
0x34b655…2a6f
4 touches
1 conflict
0x46c276ba…7f70
0x0c3a7d…1ebb
2 touches
1 conflict
0xd06cc746…27e4
0x0c3a7d…1ebb
2 touches
0 conflicts
0xfeafddae…05bd
0x188d58…ea8e
2 touches
0 conflicts
0xfeafddae…05bf
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0012
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 0x7fc8f46ef5…dd0f75
Audit this contract →
← previous block·next block →recent activity