← previous blocknext block →recent activity
Analyzing
Block #101,302,487
26 transactions · 23 stateful · 2026-09-02 10:18:22 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.19
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,302,487 · 26 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
3w010w111w215w320w022w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x2c2761c0…476e
0x34b655…2a6f
4 touches
1 conflict
0x2528e717…2a22
0x34b655…2a6f
4 touches
1 conflict
0x9d7ac3b9…22f8
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x1eb0fab5…3517
0x34b655…2a6f
2 touches
0 conflicts
0x2d02f869…1f83
0x34b655…2a6f
2 touches
0 conflicts
0x3817764d…242b
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity