← previous blocknext block →recent activity
Analyzing
Block #93,922,433
28 transactions · 26 stateful · 2026-08-07 12:41:42 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
0.82
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,922,433 · 28 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
2w03w17w08w19w110w011w112w213w314w415w518w220w021w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9cc72937…3927
0xe52b14…7230
12 touches
15 conflicts
0xf79df061…e005
0xe52b14…7230
12 touches
15 conflicts
0xa6e37efb…afc2
0xe52b14…7230
12 touches
15 conflicts
0xa6e37efb…afc0
0xe52b14…7230
12 touches
15 conflicts
0x51232c8c…f30e
0xe52b14…7230
12 touches
15 conflicts
0x51232c8c…f30c
0xe52b14…7230
12 touches
15 conflicts
0x00000000…0000
0x019883…2a9a
6 touches
3 conflicts
0xa10c86f8…4b74
0x3bd359…433a
6 touches
3 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: 0xe52b1424…bb7230
15 conflicts on slot 0x9cc72937e8…7c3927
Audit this contract →
← previous block·next block →recent activity