← previous blocknext block →recent activity
Analyzing
Block #101,302,090
22 transactions · 21 stateful · 2026-09-02 10:16:23 UTC
Parallelism
73/100
Blocked
29%
Avg conflicts / tx
0.59
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,302,090 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w014w015w118w219w320w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xec1d6663…6042
0x34b655…2a6f
6 touches
3 conflicts
0x8cf3d245…1d0d
0x34ae4d…3fc5
4 touches
1 conflict
0xa987699f…eabe
0x34ae4d…3fc5
4 touches
1 conflict
0xea7ebe9d…709e
0x34ae4d…3fc5
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity