← previous blocknext block →recent activity
Analyzing
Block #98,380,423
16 transactions · 16 stateful · 2026-08-23 04:12:56 UTC
Parallelism
56/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,380,423 · 16 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
1w02w13w26w38w411w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44163d6b…d475
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xfc24540b…6463
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc87e767e…4bba
0x34b655…2a6f
4 touches
1 conflict
0xe277a67d…ef5f
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xe9457301…83cd
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 0x44163d6b5e…1ed475
Audit this contract →
← previous block·next block →recent activity