← previous blocknext block →recent activity
Analyzing
Block #100,562,730
10 transactions · 9 stateful · 2026-08-30 20:16:12 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,562,730 · 10 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
4w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31d88d27…7617
0x34b655…2a6f
4 touches
1 conflict
0x9d22c394…c125
0x34b655…2a6f
4 touches
1 conflict
0x88b8a8b4…5e9b
0x34b655…2a6f
4 touches
1 conflict
0xf326723f…a3f6
0x34b655…2a6f
4 touches
1 conflict
0x4dcd5c8e…e6a4
0x34b655…2a6f
2 touches
0 conflicts
0x62030a81…91be
0x34b655…2a6f
2 touches
0 conflicts
0x733c7779…a647
0x34b655…2a6f
2 touches
0 conflicts
0x8d0f6884…69f1
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 0x31d88d27c1…837617
Audit this contract →
← previous block·next block →recent activity