← previous blocknext block →recent activity
Analyzing
Block #99,077,728
30 transactions · 22 stateful · 2026-08-25 15:24:03 UTC
Parallelism
90/100
Blocked
18%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,077,728 · 30 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w117w018w121w028w129w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5dc501b…8313
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xb245fe36…d765
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x496ca27e…09a0
0x065c9d…c394
2 touches
0 conflicts
0xfc765b4b…4c3a
0x065c9d…c394
2 touches
0 conflicts
0x11258774…9892
0x2a68ba…90c5
2 touches
0 conflicts
0x06e40499…165e
0x2b46c0…1669
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 0xf5dc501bf7…748313
Audit this contract →
← previous block·next block →recent activity