← previous blocknext block →recent activity
Analyzing
Block #98,423,701
13 transactions · 13 stateful · 2026-08-23 07:50:41 UTC
Parallelism
85/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,423,701 · 13 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
1w04w05w16w08w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x803bf237…2cc1
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xda976e7f…128a
0x34b655…2a6f
4 touches
1 conflict
0x0b0611f7…e63a
0x34b655…2a6f
2 touches
0 conflicts
0x10a5a231…be40
0x34b655…2a6f
2 touches
0 conflicts
0x10bc85e3…a187
0x34b655…2a6f
2 touches
0 conflicts
0x2557abf8…2901
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 0x803bf23761…972cc1
Audit this contract →
← previous block·next block →recent activity