← previous blocknext block →recent activity
Analyzing
Block #94,848,956
12 transactions · 12 stateful · 2026-08-10 18:39:18 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,848,956 · 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
1w02w13w04w05w16w08w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6c20caf…adf2
0x34b655…2a6f
4 touches
1 conflict
0xb0608dfe…083d
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2b5101ac…090b
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xd817d562…90bc
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
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 0xa6c20cafe4…9dadf2
Audit this contract →
← previous block·next block →recent activity