← previous blocknext block →recent activity
Analyzing
Block #94,903,013
13 transactions · 10 stateful · 2026-08-10 23:11:10 UTC
Parallelism
85/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,903,013 · 13 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c7f2eca…cf5e
0x34b655…2a6f
4 touches
1 conflict
0x6713b018…05f3
0x34b655…2a6f
4 touches
1 conflict
0x08cc68a2…2a59
0x34b655…2a6f
4 touches
1 conflict
0x403a2208…7839
0x1efe02…37d6
2 touches
0 conflicts
0xea02471d…1539
0x34b655…2a6f
2 touches
0 conflicts
0xeb2ab833…2bc5
0xd42a27…01c7
2 touches
0 conflicts
0xec3f1bd0…40e0
0xd42a27…01c7
2 touches
0 conflicts
0x01dbc7a9…4731
0xea1b8e…c5ec
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
1 conflict on slot 0x1c7f2eca4a…e4cf5e
Audit this contract →
← previous block·next block →recent activity