← previous blocknext block →recent activity
Analyzing
Block #98,724,441
19 transactions · 19 stateful · 2026-08-24 09:39:58 UTC
Parallelism
74/100
Blocked
32%
Avg conflicts / tx
0.32
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,724,441 · 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
4w05w16w27w38w312w417w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76ad2033…73f5
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x93c8e37f…4e7f
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd29e547b…a1dd
0x34b655…2a6f
4 touches
1 conflict
0x0562cb77…a03b
0x34b655…2a6f
4 touches
1 conflict
0x1ecdd8c5…95b3
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
1 conflict on slot 0x76ad203323…ac73f5
Audit this contract →
← previous block·next block →recent activity