← previous blocknext block →recent activity
Analyzing
Block #98,089,237
23 transactions · 22 stateful · 2026-08-22 03:47:14 UTC
Parallelism
48/100
Blocked
68%
Avg conflicts / tx
2.39
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #98,089,237 · 23 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w17w28w39w416w519w820w921w1022w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
16 touches
28 conflicts
0x7aad02c6…b979
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0xb5cddf91…0abf
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd7a09aa4…ccce
0x34b655…2a6f
6 touches
3 conflicts
0x25957369…c648
0x34b655…2a6f
6 touches
3 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
28 conflicts on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity