← previous blocknext block →recent activity
Analyzing
Block #98,013,516
33 transactions · 27 stateful · 2026-08-21 21:26:03 UTC
Parallelism
88/100
Blocked
37%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,013,516 · 33 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
1w03w04w16w29w010w011w112w014w016w017w118w019w120w121w028w029w130w231w332w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xbb3f3c…e046
6 touches
3 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
4 touches
1 conflict
0x10abefc9…c9bc
0x2b46c0…1669
4 touches
1 conflict
0x10d80fee…dbda
0x2b46c0…1669
4 touches
1 conflict
0x40970e69…da50
0x2b46c0…1669
4 touches
1 conflict
0x8cf3d245…1d0d
0x2b46c0…1669
4 touches
1 conflict
0xb05cd4f5…73d0
0x2b46c0…1669
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity