← previous blocknext block →recent activity
Analyzing
Block #98,643,388
17 transactions · 16 stateful · 2026-08-24 02:42:33 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,643,388 · 17 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
1w05w19w010w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5dc4e6c5…9490
0x8964d7…10f8
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x2a07e64e…fe77
0x754704…b603
4 touches
1 conflict
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
0x5dc4e6c5…9491
0x8964d7…10f8
3 touches
1 conflict
0xc8c615d4…5da3
0x34b655…2a6f
2 touches
0 conflicts
0xcef70a96…db44
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: 0x8964d7c9…5b10f8
1 conflict on slot 0x5dc4e6c575…a29490
Audit this contract →
← previous block·next block →recent activity