← previous blocknext block →recent activity
Analyzing
Block #101,310,059
13 transactions · 12 stateful · 2026-09-02 10:56:29 UTC
Parallelism
85/100
Blocked
25%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,310,059 · 13 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
1w02w14w07w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xe1fd24a0…eaa6
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xd1a0fe24…d4ab
0x065c9d…c394
2 touches
0 conflicts
0xabde8104…c9a9
0x2a68ba…90c5
2 touches
0 conflicts
0x06d7243a…2d20
0x34ae4d…3fc5
2 touches
0 conflicts
0x06e40499…165e
0x34ae4d…3fc5
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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity