← previous blocknext block →recent activity
Analyzing
Block #94,674,690
16 transactions · 15 stateful · 2026-08-10 04:01:13 UTC
Parallelism
69/100
Blocked
47%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,674,690 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w08w211w312w413w115w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x72c8aeb2…9921
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x12e5ded5…a9d1
0x34b655…2a6f
5 touches
3 conflicts
0x66a11a3b…0ee9
0xa6afd3…d132
4 touches
1 conflict
0x6dea4dbf…ba54
0x34b655…2a6f
4 touches
1 conflict
0xc93761d9…cfdf
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity