← previous blocknext block →recent activity
Analyzing
Block #98,506,516
14 transactions · 13 stateful · 2026-08-23 14:49:00 UTC
Parallelism
86/100
Blocked
15%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,506,516 · 14 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
1w02w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x893eb33c…6c8b
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x9654e93b…e153
0x34b655…2a6f
4 touches
1 conflict
0xc5d56ac0…6fed
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x304195a4…6d83
0x34b655…2a6f
2 touches
0 conflicts
0x3708c7bf…3c81
0x34b655…2a6f
2 touches
0 conflicts
0x3a7fb5b5…f0e5
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 0x893eb33c6f…c56c8b
Audit this contract →
← previous block·next block →recent activity