← previous blocknext block →recent activity
Analyzing
Block #101,135,968
12 transactions · 12 stateful · 2026-09-01 20:20:38 UTC
Parallelism
75/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,135,968 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w08w19w210w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9eaed5a0…9f17
0x34b655…2a6f
4 touches
1 conflict
0xa80684c9…3948
0x34b655…2a6f
4 touches
1 conflict
0xc0a4133e…6110
0x34b655…2a6f
4 touches
1 conflict
0xcd1306ad…f1b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x15953c8d…0ee6
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
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
1 conflict on slot 0x9eaed5a054…529f17
Audit this contract →
← previous block·next block →recent activity