← previous blocknext block →recent activity
Analyzing
Block #98,090,685
23 transactions · 22 stateful · 2026-08-22 03:54:31 UTC
Parallelism
91/100
Blocked
32%
Avg conflicts / tx
0.35
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,090,685 · 23 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
1w02w010w011w013w114w115w116w017w119w020w121w122w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3abe489…ebf2
0x77d53b…8080
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xdd77da90…6df4
0x34b655…2a6f
4 touches
1 conflict
0xdf1ee09d…1ffc
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x0fd2cbc5…476b
0x77d53b…8080
4 touches
1 conflict
0x35d41cf4…b7c8
0x77d53b…8080
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: 0x77d53b3b…378080
1 conflict on slot 0xe3abe4895e…e5ebf2
Audit this contract →
← previous block·next block →recent activity