← previous blocknext block →recent activity
Analyzing
Block #98,429,485
14 transactions · 14 stateful · 2026-08-23 08:19:47 UTC
Parallelism
86/100
Blocked
7%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,429,485 · 14 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
7w08w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1f7b0e66…e067
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x490e09b7…57cd
0x34b655…2a6f
4 touches
1 conflict
0xeca74ff3…a361
0x34b655…2a6f
4 touches
1 conflict
0x12f129f2…fe6b
0x2b46c0…1669
2 touches
0 conflicts
0x62811193…186d
0x2b46c0…1669
2 touches
0 conflicts
0x62811193…186e
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 0x1f7b0e6647…e3e067
Audit this contract →
← previous block·next block →recent activity