← previous blocknext block →recent activity
Analyzing
Block #100,894,394
13 transactions · 9 stateful · 2026-09-01 00:05:00 UTC
Parallelism
85/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,894,394 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfa09be5a…1e79
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x0287e69c…74b4
0x34b655…2a6f
2 touches
0 conflicts
0x08442e85…5cb9
0x34b655…2a6f
2 touches
0 conflicts
0x08be6a43…f4dc
0x34b655…2a6f
2 touches
0 conflicts
0x0c58dea3…8bf4
0x34b655…2a6f
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 0xfa09be5aaf…9b1e79
Audit this contract →
← previous block·next block →recent activity