← previous blocknext block →recent activity
Analyzing
Block #96,034,122
28 transactions · 28 stateful · 2026-08-14 22:16:24 UTC
Parallelism
53/100
Blocked
68%
Avg conflicts / tx
3.29
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #96,034,122 · 28 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w06w17w18w09w110w211w312w413w514w615w716w817w918w1019w1120w1222w224w125w226w327w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0031
0x59df86…2780
26 touches
78 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x95ea33cc…0339
0x34b655…2a6f
6 touches
3 conflicts
0x9ad325f5…cc43
0x34b655…2a6f
4 touches
1 conflict
0xa2c9330e…e167
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: 0x59df8637…6d2780
78 conflicts on slot 0x0000000000…000031
Audit this contract →
← previous block·next block →recent activity