← previous blocknext block →recent activity
Analyzing
Block #98,666,854
18 transactions · 15 stateful · 2026-08-24 04:44:52 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
0.44
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,666,854 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w07w110w212w313w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x97bd2c47…8113
0x34b655…2a6f
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x59cc5d14…f4a8
0x34b655…2a6f
4 touches
1 conflict
0x65e6e603…cb44
0x34b655…2a6f
4 touches
1 conflict
0x65e6e603…cb45
0x34b655…2a6f
4 touches
1 conflict
0x68e5627d…6f8f
0x34b655…2a6f
4 touches
1 conflict
0x6956d31b…6393
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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: Perpl
3 conflicts on slot 0x97bd2c4753…f68113
Audit this contract →
← previous block·next block →recent activity