← previous blocknext block →recent activity
Analyzing
Block #100,750,748
30 transactions · 25 stateful · 2026-08-31 12:02:00 UTC
Parallelism
87/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,750,748 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w18w09w111w012w114w115w116w017w119w220w225w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa37f24fc…37c5
0x34b655…2a6f
8 touches
6 conflicts
0x89ac61bf…9443
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xe937b6bc…8a55
0x1b6862…e19c
4 touches
1 conflict
0x561352ff…de82
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
6 conflicts on slot 0xa37f24fcc7…7b37c5
Audit this contract →
← previous block·next block →recent activity