← previous blocknext block →recent activity
Analyzing
Block #98,024,058
19 transactions · 18 stateful · 2026-08-21 22:19:16 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.42
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,024,058 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w17w08w210w313w114w215w316w417w518w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd7443f37…eb79
0x34b655…2a6f
6 touches
3 conflicts
0x464a82ff…41de
0x34b655…2a6f
4 touches
1 conflict
0x4705062a…84be
0x34b655…2a6f
4 touches
1 conflict
0x5a7babd2…ace2
0x34b655…2a6f
4 touches
1 conflict
0x6c60fbcf…8744
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
15 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity