← previous blocknext block →recent activity
Analyzing
Block #101,894,642
16 transactions · 16 stateful · 2026-09-04 11:57:34 UTC
Parallelism
50/100
Blocked
44%
Avg conflicts / tx
1.19
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,894,642 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w37w48w010w513w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x72d35c7e…525e
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x74e46435…fdcd
0x34b655…2a6f
8 touches
6 conflicts
0xc8c615d4…5da3
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x976029c0…a4de
0x34b655…2a6f
6 touches
3 conflicts
0xd62f3741…b903
0x34b655…2a6f
6 touches
3 conflicts
0xd41f5136…97c6
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x72d35c7e72…07525e
Audit this contract →
← previous block·next block →recent activity