← previous blocknext block →recent activity
Analyzing
Block #94,743,634
15 transactions · 14 stateful · 2026-08-10 09:48:45 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,743,634 · 15 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
2w03w15w06w17w28w09w110w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x93b6fab0…09d6
0x34b655…2a6f
8 touches
6 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x47ed8e43…8a8a
0x851145…3f07
4 touches
1 conflict
0xef05b756…d18f
0x851145…3f07
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x7e95fe64…7024
0x851145…3f07
3 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
6 conflicts on slot 0x93b6fab01a…2d09d6
Audit this contract →
← previous block·next block →recent activity