← previous blocknext block →recent activity
Analyzing
Block #100,725,306
23 transactions · 20 stateful · 2026-08-31 09:54:01 UTC
Parallelism
91/100
Blocked
15%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,725,306 · 23 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
2w04w010w011w119w121w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68531239…e9a3
0x34b655…2a6f
4 touches
1 conflict
0x77c29121…484f
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xda3eb3c3…9d60
0x34b655…2a6f
4 touches
1 conflict
0xdcd8147b…ad88
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x42522e76…2592
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
1 conflict on slot 0x68531239f9…5ae9a3
Audit this contract →
← previous block·next block →recent activity