← previous blocknext block →recent activity
Analyzing
Block #99,954,718
21 transactions · 20 stateful · 2026-08-28 17:12:17 UTC
Parallelism
81/100
Blocked
15%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,954,718 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w010w011w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x758a0dd5…0f46
0x34b655…2a6f
6 touches
3 conflicts
0xf26a1736…a588
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xa6d40b7f…2969
0x34b655…2a6f
4 touches
1 conflict
0x844b7221…5ad8
0x34b655…2a6f
4 touches
1 conflict
0x69411fb3…e36d
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
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
3 conflicts on slot 0x758a0dd50c…2a0f46
Audit this contract →
← previous block·next block →recent activity