← previous blocknext block →recent activity
Analyzing
Block #101,017,527
26 transactions · 23 stateful · 2026-09-01 10:24:27 UTC
Parallelism
81/100
Blocked
26%
Avg conflicts / tx
0.35
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,017,527 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w19w010w111w215w316w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd401e7c2…12fd
0x34b655…2a6f
8 touches
6 conflicts
0x898d9b8a…d1ef
0x34b655…2a6f
6 touches
3 conflicts
0xdfce7dfe…5053
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x4e135144…4167
0x34b655…2a6f
4 touches
1 conflict
0x8db32935…81a7
0x34b655…2a6f
4 touches
1 conflict
0x950e74f7…2a34
0x34b655…2a6f
4 touches
1 conflict
0xa29f9f69…ef45
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 0xd401e7c26c…f212fd
Audit this contract →
← previous block·next block →recent activity