← previous blocknext block →recent activity
Analyzing
Block #94,859,134
12 transactions · 12 stateful · 2026-08-10 19:30:30 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,859,134 · 12 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
1w02w17w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5ea108a…dbf6
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x4b8f0c69…87d3
0x34b655…2a6f
2 touches
0 conflicts
0x66401d81…7a05
0x34b655…2a6f
2 touches
0 conflicts
0x875ad1ab…8c8a
0x34b655…2a6f
2 touches
0 conflicts
0x98a7af9d…ff97
0x34b655…2a6f
2 touches
0 conflicts
0xabb0951a…273a
0x34b655…2a6f
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 0xf5ea108a6a…e5dbf6
Audit this contract →
← previous block·next block →recent activity