← previous blocknext block →recent activity
Analyzing
Block #98,677,633
19 transactions · 19 stateful · 2026-08-24 05:41:07 UTC
Parallelism
79/100
Blocked
32%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,677,633 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w07w211w012w117w118w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd459bf7b…92c3
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xefeb7937…c283
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5202eeec…466f
0x34b655…2a6f
4 touches
1 conflict
0xa02838a3…bc54
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
1 conflict on slot 0xd459bf7bc2…d392c3
Audit this contract →
← previous block·next block →recent activity