← previous blocknext block →recent activity
Analyzing
Block #100,920,877
12 transactions · 11 stateful · 2026-09-01 02:18:12 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,920,877 · 12 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
1w02w15w07w18w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3da1337e…9c84
0x34b655…2a6f
8 touches
6 conflicts
0x2827ae77…4368
0x34b655…2a6f
6 touches
3 conflicts
0xf6b6a764…04cc
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
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 0x3da1337e2b…3c9c84
Audit this contract →
← previous block·next block →recent activity