← previous blocknext block →recent activity
Analyzing
Block #98,101,056
25 transactions · 23 stateful · 2026-08-22 04:46:43 UTC
Parallelism
84/100
Blocked
39%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,101,056 · 25 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
3w04w05w07w08w09w111w114w115w216w117w119w320w224w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x48cb599a…c21c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4abfb389…18f4
0x34b655…2a6f
4 touches
1 conflict
0x5655f5c3…6b75
0x34b655…2a6f
4 touches
1 conflict
0x7c09c53e…64b4
0x34b655…2a6f
4 touches
1 conflict
0x823a7ba9…34c9
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 0x48cb599a7b…38c21c
Audit this contract →
← previous block·next block →recent activity