← previous blocknext block →recent activity
Analyzing
Block #98,647,641
10 transactions · 10 stateful · 2026-08-24 03:04:35 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,647,641 · 10 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
2w04w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56f12a77…7c62
0x34b655…2a6f
4 touches
1 conflict
0xab41643c…f9bf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x2504e58e…35a9
0x34b655…2a6f
2 touches
0 conflicts
0x3e3f27ce…580c
0x34b655…2a6f
2 touches
0 conflicts
0x41bfea99…ac66
0x34b655…2a6f
2 touches
0 conflicts
0x42522e76…2592
0x34b655…2a6f
2 touches
0 conflicts
0x42522e76…2593
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: Perpl
1 conflict on slot 0x56f12a7768…3d7c62
Audit this contract →
← previous block·next block →recent activity