← previous blocknext block →recent activity
Analyzing
Block #94,235,714
17 transactions · 16 stateful · 2026-08-08 15:02:07 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,235,714 · 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
2w03w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cc0e9c8…3ae6
0x34b655…2a6f
4 touches
1 conflict
0x3651d66e…b5e9
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x8f1164bf…9095
0x34b655…2a6f
4 touches
1 conflict
0xd211fb68…42f9
0x34b655…2a6f
4 touches
1 conflict
0xe283e878…7262
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
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 0x5cc0e9c8b0…1d3ae6
Audit this contract →
← previous block·next block →recent activity