← previous blocknext block →recent activity
Analyzing
Block #94,914,045
7 transactions · 6 stateful · 2026-08-11 00:06:39 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,914,045 · 7 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07b86c51…cdae
0x2a68ba…90c5
4 touches
1 conflict
0x11b69a7e…334e
0x01bff4…1071
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x7a3d9715…455c
0x851145…3f07
4 touches
1 conflict
0xd82f3ce2…5c31
0x01bff4…1071
2 touches
0 conflicts
0xe78a9e4b…ec2b
0x01bff4…1071
2 touches
0 conflicts
0xf13704e6…258a
0x01bff4…1071
2 touches
0 conflicts
0x0c9249f6…6bce
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: Kuru Exchange: MarginAccount
1 conflict on slot 0x07b86c515d…73cdae
Audit this contract →
← previous block·next block →recent activity