← previous blocknext block →recent activity
Analyzing
Block #98,551,570
19 transactions · 18 stateful · 2026-08-23 18:44:11 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
0.79
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,551,570 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w17w18w09w210w311w412w113w014w117w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x1408e7c7…f324
0x34b655…2a6f
6 touches
3 conflicts
0x080c3a8a…3088
0x34b655…2a6f
4 touches
1 conflict
0xd2838cc2…8be3
0x34b655…2a6f
4 touches
1 conflict
0x67a56c8b…f955
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x8590b692…b267
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
10 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity