← previous blocknext block →recent activity
Analyzing
Block #94,250,283
13 transactions · 12 stateful · 2026-08-08 16:16:03 UTC
Parallelism
77/100
Blocked
25%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,250,283 · 13 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
1w02w17w08w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64ac7e40…5d7d
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc9c603ba…3c4a
0x34b655…2a6f
4 touches
1 conflict
0x4fade30b…c659
0xd32edf…ff58
3 touches
1 conflict
0x0506543e…b043
0x065c9d…c394
2 touches
0 conflicts
0x371f974c…1109
0x065c9d…c394
2 touches
0 conflicts
0x5540f956…69e8
0x065c9d…c394
2 touches
0 conflicts
0x5b155cf8…da5d
0x065c9d…c394
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
3 conflicts on slot 0x64ac7e4028…765d7d
Audit this contract →
← previous block·next block →recent activity