← previous blocknext block →recent activity
Analyzing
Block #101,662,364
15 transactions · 13 stateful · 2026-09-03 16:29:02 UTC
Parallelism
73/100
Blocked
31%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,662,364 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w07w18w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e1a47b0…a852
0x34b655…2a6f
6 touches
3 conflicts
0xefb236ca…f49b
0x34b655…2a6f
6 touches
3 conflicts
0xc7493474…4601
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x5906754f…b584
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xda9ed379…b8d1
0x34b655…2a6f
4 touches
1 conflict
0x0643b816…53ca
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
3 conflicts on slot 0x5e1a47b057…48a852
Audit this contract →
← previous block·next block →recent activity