← previous blocknext block →recent activity
Analyzing
Block #94,318,212
35 transactions · 25 stateful · 2026-08-08 22:00:11 UTC
Parallelism
80/100
Blocked
48%
Avg conflicts / tx
1.03
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,318,212 · 35 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w28w39w311w012w115w016w119w125w126w427w132w533w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a57a2b8…3cdd
0x34b655…2a6f
14 touches
21 conflicts
0x5502e1cc…3910
0x34b655…2a6f
8 touches
6 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x5ab74544…e16c
0x34b655…2a6f
4 touches
1 conflict
0x6f28eb14…e5ef
0x34b655…2a6f
4 touches
1 conflict
0x76196ad0…ce0c
0x34b655…2a6f
4 touches
1 conflict
0x78f16adf…3249
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
21 conflicts on slot 0x0a57a2b8cd…773cdd
Audit this contract →
← previous block·next block →recent activity