← previous blocknext block →recent activity
Analyzing
Block #106,381,872
17 transactions · 13 stateful · 2026-09-20 05:38:57 UTC
Parallelism
88/100
Blocked
15%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,381,872 · 17 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
1w04w012w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4681609f…6493
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x67c1fa4a…0515
0x065c9d…c394
3 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0x8765edd1…a7d5
0x34b655…2a6f
2 touches
0 conflicts
0xdb3937e8…23cb
0x34b655…2a6f
2 touches
0 conflicts
0xf039e2f8…3d8a
0x34b655…2a6f
2 touches
0 conflicts
0x5d82c9b5…004c
0x3bd359…433a
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 0x4681609fd4…e96493
Audit this contract →
← previous block·next block →recent activity