← previous blocknext block →recent activity
Analyzing
Block #98,988,495
17 transactions · 17 stateful · 2026-08-25 07:48:45 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,988,495 · 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
2w03w16w07w18w09w012w113w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea48b4c6…3547
0x8964d7…10f8
4 touches
1 conflict
0xea48b4c6…3540
0x8964d7…10f8
4 touches
1 conflict
0xea48b4c6…3541
0x8964d7…10f8
4 touches
1 conflict
0xea48b4c6…3544
0x8964d7…10f8
4 touches
1 conflict
0xea48b4c6…3545
0x8964d7…10f8
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xb5c7c6aa…fdba
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: 0x8964d7c9…5b10f8
1 conflict on slot 0xea48b4c648…603547
Audit this contract →
← previous block·next block →recent activity