← previous blocknext block →recent activity
Analyzing
Block #94,230,396
14 transactions · 13 stateful · 2026-08-08 14:35:04 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,230,396 · 14 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
3w04w16w28w39w010w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x53d526f9…1ab8
0x34b655…2a6f
6 touches
3 conflicts
0xb8506b7b…db57
0x968279…9342
4 touches
1 conflict
0xb8506b7b…db54
0x968279…9342
4 touches
1 conflict
0xb8506b7b…db55
0x968279…9342
4 touches
1 conflict
0x94f2c3b4…4ef6
0x34b655…2a6f
4 touches
1 conflict
0xb91a6f59…722c
0x34b655…2a6f
4 touches
1 conflict
0xe969b395…ceea
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
3 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity