← previous blocknext block →recent activity
Analyzing
Block #94,964,969
10 transactions · 10 stateful · 2026-08-11 04:22:47 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,964,969 · 10 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
2w03w04w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f447bf3…57c7
0x34b655…2a6f
4 touches
1 conflict
0x9aed14df…5b2b
0x34b655…2a6f
4 touches
1 conflict
0xb7af4d9e…c348
0x34b655…2a6f
4 touches
1 conflict
0xbc8d2ca3…f2c1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe732567d…b65d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x8e3a84e4…4686
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 0x5f447bf375…cc57c7
Audit this contract →
← previous block·next block →recent activity