← previous blocknext block →recent activity
Analyzing
Block #98,420,491
19 transactions · 17 stateful · 2026-08-23 07:34:32 UTC
Parallelism
74/100
Blocked
29%
Avg conflicts / tx
0.37
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,420,491 · 19 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
2w04w05w17w211w012w114w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35f60aa4…b872
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x36126dcb…ca1e
0x34b655…2a6f
4 touches
1 conflict
0x513b12c7…47cd
0x34b655…2a6f
4 touches
1 conflict
0x31d88d27…7617
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x5164ab0e…01e1
0xc8689a…ee79
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 0x35f60aa478…f1b872
Audit this contract →
← previous block·next block →recent activity