← previous blocknext block →recent activity
Analyzing
Block #98,075,033
12 transactions · 12 stateful · 2026-08-22 02:35:46 UTC
Parallelism
67/100
Blocked
42%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,075,033 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w06w17w18w09w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x065ff70b…356d
0x40c49f…2af0
4 touches
1 conflict
0xbf5b671c…a44f
0x40c49f…2af0
4 touches
1 conflict
0xc9a06450…d07e
0x40c49f…2af0
4 touches
1 conflict
0x70d81211…f49f
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
3 conflicts on slot 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity