← previous blocknext block →recent activity
Analyzing
Block #94,980,631
13 transactions · 13 stateful · 2026-08-11 05:41:33 UTC
Parallelism
54/100
Blocked
54%
Avg conflicts / tx
1.38
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,980,631 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w06w17w28w39w410w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x968279…9342
12 touches
15 conflicts
0xd69c490b…7579
0x968279…9342
12 touches
15 conflicts
0xd69c490b…7577
0x968279…9342
12 touches
15 conflicts
0xd69c490b…7576
0x968279…9342
12 touches
15 conflicts
0xd69c490b…7573
0x968279…9342
12 touches
15 conflicts
0xd69c490b…7572
0x968279…9342
12 touches
15 conflicts
0x32d272f3…a93b
0x968279…9342
12 touches
15 conflicts
0x32d272f3…a939
0x968279…9342
12 touches
15 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: 0x96827978…f09342
15 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity