← previous blocknext block →recent activity
Analyzing
Block #106,207,809
25 transactions · 23 stateful · 2026-09-19 15:02:56 UTC
Parallelism
80/100
Blocked
57%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,207,809 · 25 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
1w03w04w15w16w27w08w010w011w112w113w214w315w016w117w219w420w123w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x315e07b8…9823
0x34b655…2a6f
8 touches
6 conflicts
0xaef82336…d052
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x174d81f5…6cef
0x34b655…2a6f
6 touches
3 conflicts
0x3bb4ea6a…2370
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x36901f6b…925c
0x34b655…2a6f
4 touches
1 conflict
0xff675495…5381
0x34b655…2a6f
4 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
6 conflicts on slot 0x315e07b806…529823
Audit this contract →
← previous block·next block →recent activity