← previous blocknext block →recent activity
Analyzing
Block #101,990,857
18 transactions · 17 stateful · 2026-09-04 20:05:36 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,990,857 · 18 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
1w02w15w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86cea35b…bdff
0x34b655…2a6f
4 touches
1 conflict
0xf9332b7d…3c53
0x34b655…2a6f
4 touches
1 conflict
0x0dd76119…dd97
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x3c67d31e…3dbe
0x34b655…2a6f
4 touches
1 conflict
0x4bfdcd51…9b58
0x34b655…2a6f
4 touches
1 conflict
0x581b829b…9578
0x34b655…2a6f
4 touches
1 conflict
0x2aedda45…3d7f
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 0x86cea35b12…8ebdff
Audit this contract →
← previous block·next block →recent activity