← previous blocknext block →recent activity
Analyzing
Block #100,018,988
9 transactions · 9 stateful · 2026-08-28 22:35:58 UTC
Parallelism
44/100
Blocked
44%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,018,988 · 9 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x30d3b573…4288
0x34b655…2a6f
8 touches
6 conflicts
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x6cb5409a…dcb3
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xee3c706e…62ed
0x34b655…2a6f
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002b
0x1b6862…e19c
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
6 conflicts on slot 0x30d3b573cd…284288
Audit this contract →
← previous block·next block →recent activity