← previous blocknext block →recent activity
Analyzing
Block #106,110,081
13 transactions · 11 stateful · 2026-09-19 06:51:03 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,110,081 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4d37162…967c
0x34b655…2a6f
6 touches
3 conflicts
0x809f2ba8…89d3
0x34b655…2a6f
4 touches
1 conflict
0x0db691ab…3ee3
0x34b655…2a6f
4 touches
1 conflict
0xab981df1…2941
0x34b655…2a6f
4 touches
1 conflict
0xba1edffb…323e
0x34b655…2a6f
4 touches
1 conflict
0xbc417c5e…4f97
0x34b655…2a6f
4 touches
1 conflict
0x16867f4f…0bb3
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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
3 conflicts on slot 0xa4d371626a…aa967c
Audit this contract →
← previous block·next block →recent activity