← previous blocknext block →recent activity
Analyzing
Block #106,252,245
16 transactions · 15 stateful · 2026-09-19 18:46:37 UTC
Parallelism
69/100
Blocked
53%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,252,245 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w09w310w111w112w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0547a894…b48b
0x34b655…2a6f
10 touches
10 conflicts
0x7cf3eb0f…06c5
0x34b655…2a6f
8 touches
6 conflicts
0x76ed8777…1e5f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0xe2ecec55…b797
0x34b655…2a6f
6 touches
3 conflicts
0xba5743c7…21c6
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 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
10 conflicts on slot 0x0547a8949d…19b48b
Audit this contract →
← previous block·next block →recent activity