← previous blocknext block →recent activity
Analyzing
Block #100,589,835
19 transactions · 15 stateful · 2026-08-30 22:32:33 UTC
Parallelism
74/100
Blocked
47%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,589,835 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w18w011w112w215w316w118w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4018694e…cf1d
0x34b655…2a6f
8 touches
6 conflicts
0xd8ca1bc1…cbcc
0x34b655…2a6f
6 touches
3 conflicts
0xef3f5637…f47c
0x34b655…2a6f
6 touches
3 conflicts
0xa6464996…3af9
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x0217a039…5d4c
0x34b655…2a6f
6 touches
3 conflicts
0x81716ce9…095f
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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 0x4018694e95…4ccf1d
Audit this contract →
← previous block·next block →recent activity