← previous blocknext block →recent activity
Analyzing
Block #101,893,993
8 transactions · 8 stateful · 2026-09-04 11:54:16 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,893,993 · 8 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4abfb389…18f4
0x34b655…2a6f
4 touches
1 conflict
0xf5d9f22d…e99f
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x01315072…0e2d
0x34b655…2a6f
2 touches
0 conflicts
0x04d4f30d…4dfb
0x34b655…2a6f
2 touches
0 conflicts
0x1ced1ca4…41c7
0x34b655…2a6f
2 touches
0 conflicts
0x1d3cdb64…f49c
0x34b655…2a6f
2 touches
0 conflicts
0x23ef5772…6bb0
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 0x4abfb3894a…c318f4
Audit this contract →
← previous block·next block →recent activity