← previous blocknext block →recent activity
Analyzing
Block #98,538,711
23 transactions · 23 stateful · 2026-08-23 17:37:01 UTC
Parallelism
91/100
Blocked
13%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,538,711 · 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
3w05w06w110w117w021w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x8c49c85c…ee96
0x34b655…2a6f
4 touches
1 conflict
0x0e4000ee…afb9
0x34b655…2a6f
4 touches
1 conflict
0xa605468c…1bfc
0x2b46c0…1669
2 touches
0 conflicts
0x0e18d182…0425
0x34b655…2a6f
2 touches
0 conflicts
0x32c3536c…e1c1
0x34b655…2a6f
2 touches
0 conflicts
0x34d95d94…3a16
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 0x51fc8795c8…571266
Audit this contract →
← previous block·next block →recent activity