← previous blocknext block →recent activity
Analyzing
Block #101,300,539
20 transactions · 13 stateful · 2026-09-02 10:08:34 UTC
Parallelism
80/100
Blocked
23%
Avg conflicts / tx
0.2
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,300,539 · 20 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
10w011w117w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x2ad2f4bc…1800
0x34b655…2a6f
4 touches
1 conflict
0xbe55ebc6…d23d
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x04be98f0…f405
0x34b655…2a6f
2 touches
0 conflicts
0x0fd85426…75a1
0x34b655…2a6f
2 touches
0 conflicts
0x232df012…c608
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