← previous blocknext block →recent activity
Analyzing
Block #101,674,256
10 transactions · 9 stateful · 2026-09-03 17:28:52 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,674,256 · 10 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
1w06w07w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe136af8f…e687
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0x0bc69602…4198
0x34b655…2a6f
2 touches
0 conflicts
0x0ffac39e…6d34
0x34b655…2a6f
2 touches
0 conflicts
0x10a4a35a…55e4
0x34b655…2a6f
2 touches
0 conflicts
0x1c0b6641…28c3
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 0xe136af8f54…69e687
Audit this contract →
← previous block·next block →recent activity