← previous blocknext block →recent activity
Analyzing
Block #106,413,484
13 transactions · 11 stateful · 2026-09-20 08:18:02 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,413,484 · 13 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0505bae8…b4fb
0x34b655…2a6f
4 touches
1 conflict
0x6da5efbe…7e01
0x34b655…2a6f
4 touches
1 conflict
0x8d664414…3344
0x34b655…2a6f
4 touches
1 conflict
0xe283e878…7262
0x34b655…2a6f
4 touches
1 conflict
0x5cc231f5…f1cd
0x34ae4d…3fc5
2 touches
0 conflicts
0x8cf3d245…1d0d
0x34ae4d…3fc5
2 touches
0 conflicts
0xe2263bea…6a9f
0x34ae4d…3fc5
2 touches
0 conflicts
0xe2263bea…6aa0
0x34ae4d…3fc5
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 0x0505bae898…14b4fb
Audit this contract →
← previous block·next block →recent activity