← previous blocknext block →recent activity
Analyzing
Block #100,612,932
10 transactions · 10 stateful · 2026-08-31 00:28:45 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,612,932 · 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
4w06w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x26dddc8a…b005
0x34b655…2a6f
4 touches
1 conflict
0x5a548af5…0eb0
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0009
0x32681b…919f
2 touches
0 conflicts
0x00000000…000c
0x32681b…919f
2 touches
0 conflicts
0x0363f3d8…dc1c
0x32681b…919f
2 touches
0 conflicts
0x0f8a9187…89f4
0x32681b…919f
2 touches
0 conflicts
0x1063e8e2…aeed
0x32681b…919f
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity