← previous blocknext block →recent activity
Analyzing
Block #106,388,533
15 transactions · 12 stateful · 2026-09-20 06:12:28 UTC
Parallelism
87/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,388,533 · 15 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
1w02w03w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d9021c2…898f
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x0262e1c6…52e1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0490581d…adaf
0x34b655…2a6f
2 touches
0 conflicts
0x165d6ec5…b2d2
0x34b655…2a6f
2 touches
0 conflicts
0x2e9d65ac…2265
0x34b655…2a6f
2 touches
0 conflicts
0x3cb7ee74…b8a5
0x34b655…2a6f
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 0x8d9021c2b4…2e898f
Audit this contract →
← previous block·next block →recent activity