← previous blocknext block →recent activity
Analyzing
Block #94,835,138
15 transactions · 14 stateful · 2026-08-10 17:29:47 UTC
Parallelism
87/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,835,138 · 15 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
2w03w19w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e8ddd73…4dfb
0x34b655…2a6f
4 touches
1 conflict
0x78b52df8…344b
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc1aa38d0…a9f3
0x34b655…2a6f
4 touches
1 conflict
0xdd47c927…2654
0x34b655…2a6f
4 touches
1 conflict
0x3a07a361…ab39
0x34b655…2a6f
4 touches
1 conflict
0xc41ae364…920b
0x065c9d…c394
2 touches
0 conflicts
0xf6d34cc6…0ced
0x065c9d…c394
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 0x5e8ddd735e…694dfb
Audit this contract →
← previous block·next block →recent activity