← previous blocknext block →recent activity
Analyzing
Block #99,488,143
34 transactions · 27 stateful · 2026-08-27 01:50:03 UTC
Parallelism
88/100
Blocked
33%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,488,143 · 34 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
1w03w04w15w010w011w112w213w017w124w127w231w132w233w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00500a94…20d5
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x7b48bd22…c0f3
0xd32edf…ff58
5 touches
3 conflicts
0x5c455afd…ce06
0x34b655…2a6f
4 touches
1 conflict
0x5db96e85…83ed
0x065c9d…c394
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x92385428…6941
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 0x00500a94bf…5a20d5
Audit this contract →
← previous block·next block →recent activity