← previous blocknext block →recent activity
Analyzing
Block #94,836,992
16 transactions · 14 stateful · 2026-08-10 17:39:06 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,836,992 · 16 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
2w03w14w17w08w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf28a9fc2…05e4
0x34b655…2a6f
6 touches
3 conflicts
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x4a5956ef…e226
0x34b655…2a6f
4 touches
1 conflict
0x589623ea…8ce2
0x34b655…2a6f
4 touches
1 conflict
0x65161043…bcf5
0x34b655…2a6f
4 touches
1 conflict
0x6d8577dd…194a
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
3 conflicts on slot 0xf28a9fc232…c905e4
Audit this contract →
← previous block·next block →recent activity