← previous blocknext block →recent activity
Analyzing
Block #101,668,363
18 transactions · 11 stateful · 2026-09-03 16:59:13 UTC
Parallelism
89/100
Blocked
9%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,668,363 · 18 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
4w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xf1eadfaf…34e5
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x110a3804…f842
0x34b655…2a6f
2 touches
0 conflicts
0x27291114…54d1
0x34b655…2a6f
2 touches
0 conflicts
0x2748f498…f1c1
0x34b655…2a6f
2 touches
0 conflicts
0x2fd1b088…422f
0x34b655…2a6f
2 touches
0 conflicts
0x30a65b14…dfe2
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 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity