← previous blocknext block →recent activity
Analyzing
Block #101,895,888
7 transactions · 7 stateful · 2026-09-04 12:03:53 UTC
Parallelism
43/100
Blocked
43%
Avg conflicts / tx
0.86
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,895,888 · 7 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
1w02w14w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc23706e5…704a
0x34b655…2a6f
4 touches
1 conflict
0xc0a73ae2…2e95
0x34b655…2a6f
4 touches
1 conflict
0xce06a0f7…efef
0x34b655…2a6f
3 touches
1 conflict
0x52b2837f…4b7f
0x34b655…2a6f
3 touches
1 conflict
0x7f5b2c1d…0e7f
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
6 conflicts on slot 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity