← previous blocknext block →recent activity
Analyzing
Block #98,423,734
18 transactions · 16 stateful · 2026-08-23 07:50:51 UTC
Parallelism
89/100
Blocked
13%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,423,734 · 18 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w09w010w111w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd0efe734…3cb7
0x34b655…2a6f
4 touches
1 conflict
0xf3b253be…78b5
0x34b655…2a6f
4 touches
1 conflict
0x2557abf8…2901
0x34b655…2a6f
4 touches
1 conflict
0x2b78ba10…9ce5
0x34b655…2a6f
4 touches
1 conflict
0x4c23cdee…8c52
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x46279ae7…20dd
0x2b46c0…1669
2 touches
0 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
1 conflict on slot 0xd0efe734d9…ae3cb7
Audit this contract →
← previous block·next block →recent activity