← previous blocknext block →recent activity
Analyzing
Block #94,716,985
12 transactions · 11 stateful · 2026-08-10 07:33:57 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,716,985 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41377979…0a18
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x0a2131b3…455e
0x34b655…2a6f
2 touches
0 conflicts
0x29eb4d5c…a77c
0x34b655…2a6f
2 touches
0 conflicts
0x382baa9b…db1c
0x34b655…2a6f
2 touches
0 conflicts
0x4ca2a6c3…ab80
0x34b655…2a6f
2 touches
0 conflicts
0x4d58476d…3e80
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 0x413779793d…8f0a18
Audit this contract →
← previous block·next block →recent activity