← previous blocknext block →recent activity
Analyzing
Block #100,858,528
17 transactions · 14 stateful · 2026-08-31 21:04:35 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,858,528 · 17 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
2w010w013w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3bfb961d…1dee
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xf66069d2…af53
0x065c9d…c394
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x264e7309…1790
0x065c9d…c394
3 touches
1 conflict
0x294269fc…7e7e
0x065c9d…c394
2 touches
1 conflict
0x3c78ca04…432c
0x34b655…2a6f
2 touches
0 conflicts
0x687efc1e…3244
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 0x3bfb961d86…e91dee
Audit this contract →
← previous block·next block →recent activity