← previous blocknext block →recent activity
Analyzing
Block #100,234,750
20 transactions · 18 stateful · 2026-08-29 16:42:17 UTC
Parallelism
70/100
Blocked
39%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,234,750 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w113w014w116w217w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xb9b4eff6…c3ef
0x34b655…2a6f
6 touches
3 conflicts
0x1ffbed17…4f3b
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x4732814e…7dfd
0x34b655…2a6f
4 touches
1 conflict
0x56a284d9…32e4
0x34b655…2a6f
4 touches
1 conflict
0x62910921…3016
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
3 conflicts on slot 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity