← previous blocknext block →recent activity
Analyzing
Block #101,990,962
10 transactions · 10 stateful · 2026-09-04 20:06:10 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,990,962 · 10 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
2w04w15w28w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x08c5d8d8…c7c1
0x34b655…2a6f
4 touches
1 conflict
0x6be05f69…33d9
0x34b655…2a6f
4 touches
1 conflict
0x8fd9063d…2f57
0x34b655…2a6f
4 touches
1 conflict
0xc00be471…2449
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x325dc2d3…ce2f
0x34b655…2a6f
2 touches
0 conflicts
0x32f13877…1e2a
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity