← previous blocknext block →recent activity
Analyzing
Block #98,421,393
16 transactions · 16 stateful · 2026-08-23 07:39:05 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,421,393 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w09w011w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2db6e7a…d074
0x34b655…2a6f
4 touches
1 conflict
0xcdd556aa…31d0
0x34b655…2a6f
4 touches
1 conflict
0x515a6424…89cf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x6a34000e…a981
0x34b655…2a6f
2 touches
0 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
2 touches
0 conflicts
0x803bf237…2cc1
0x34b655…2a6f
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
1 conflict on slot 0xc2db6e7a2c…ddd074
Audit this contract →
← previous block·next block →recent activity