← previous blocknext block →recent activity
Analyzing
Block #98,667,353
12 transactions · 11 stateful · 2026-08-24 04:47:29 UTC
Parallelism
58/100
Blocked
36%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,667,353 · 12 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb63ef486…0dcc
0x34b655…2a6f
8 touches
6 conflicts
0x73223e6d…ed70
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x6c10a7b2…0e4b
0x34b655…2a6f
4 touches
1 conflict
0x2f74f175…9285
0x2b46c0…1669
2 touches
0 conflicts
0x2f74f175…9287
0x2b46c0…1669
2 touches
0 conflicts
0x46279ae7…20dd
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
6 conflicts on slot 0xb63ef48684…2d0dcc
Audit this contract →
← previous block·next block →recent activity