← previous blocknext block →recent activity
Analyzing
Block #94,718,839
12 transactions · 12 stateful · 2026-08-10 07:43:17 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,718,839 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a100ac0…96d3
0x34b655…2a6f
4 touches
1 conflict
0xb9b077a8…e029
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xbde1af1b…9adf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x1b25f260…c429
0x34b655…2a6f
2 touches
0 conflicts
0x3111a64f…eb7f
0x34b655…2a6f
2 touches
0 conflicts
0x379dc435…6616
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 0x5a100ac0d9…2396d3
Audit this contract →
← previous block·next block →recent activity