← previous blocknext block →recent activity
Analyzing
Block #98,261,728
27 transactions · 25 stateful · 2026-08-22 18:15:46 UTC
Parallelism
85/100
Blocked
36%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,261,728 · 27 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
2w03w08w09w010w111w016w117w219w122w123w224w325w326w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea57afd0…4232
0x34b655…2a6f
8 touches
6 conflicts
0xdd2c59b1…780f
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x3e49348b…9445
0x34b655…2a6f
4 touches
1 conflict
0x4f4bdabd…ffba
0x34b655…2a6f
4 touches
1 conflict
0x5e8223c2…c242
0x34b655…2a6f
4 touches
1 conflict
0x73a33694…9d5d
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
6 conflicts on slot 0xea57afd097…7f4232
Audit this contract →
← previous block·next block →recent activity