← previous blocknext block →recent activity
Analyzing
Block #94,853,564
17 transactions · 15 stateful · 2026-08-10 19:02:29 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,853,564 · 17 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
2w07w010w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x589623ea…8ce2
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd0f640aa…5f5c
0x34b655…2a6f
4 touches
1 conflict
0xd957c18f…5cfc
0x34b655…2a6f
4 touches
1 conflict
0x0a0cecef…4ed0
0x34b655…2a6f
4 touches
1 conflict
0x2c66ecd1…f41d
0x34b655…2a6f
4 touches
1 conflict
0x3e45f694…f713
0x34b655…2a6f
4 touches
1 conflict
0x4e55c12b…0421
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
1 conflict on slot 0x589623eaa3…c68ce2
Audit this contract →
← previous block·next block →recent activity