← previous blocknext block →recent activity
Analyzing
Block #94,300,346
13 transactions · 12 stateful · 2026-08-08 20:29:33 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,300,346 · 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
2w03w04w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c7c65d0…0b52
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x9a09cf4e…f19f
0x34b655…2a6f
4 touches
1 conflict
0xf3383813…4a0c
0x34b655…2a6f
4 touches
1 conflict
0x06e45d39…781e
0x34b655…2a6f
4 touches
1 conflict
0xbf530e70…e3e4
0x065c9d…c394
2 touches
0 conflicts
0xc161c03d…7cb5
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
0x2b46c0…1669
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 0x3c7c65d0e6…a00b52
Audit this contract →
← previous block·next block →recent activity