← previous blocknext block →recent activity
Analyzing
Block #94,810,427
17 transactions · 17 stateful · 2026-08-10 15:25:27 UTC
Parallelism
88/100
Blocked
18%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,810,427 · 17 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
1w02w13w17w015w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd87d6567…2ed0
0x34b655…2a6f
4 touches
1 conflict
0xd93edb3f…94ec
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x9fb57027…272f
0x34b655…2a6f
4 touches
1 conflict
0xa6b89ebb…a66e
0x34b655…2a6f
4 touches
1 conflict
0x4acbdbcf…a8c6
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x56133b91…a672
0x34b655…2a6f
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 0xd87d6567b3…9e2ed0
Audit this contract →
← previous block·next block →recent activity