← previous blocknext block →recent activity
Analyzing
Block #93,674,489
18 transactions · 18 stateful · 2026-08-06 15:54:45 UTC
Parallelism
72/100
Blocked
44%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,674,489 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w16w07w28w09w110w211w113w314w417w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6e37efb…afc2
0xe52b14…7230
6 touches
3 conflicts
0xe1902c61…65ad
0xe52b14…7230
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xe1902c61…65af
0xe52b14…7230
6 touches
3 conflicts
0xf79df061…e005
0xe52b14…7230
6 touches
3 conflicts
0xa6e37efb…afc0
0xe52b14…7230
6 touches
3 conflicts
0x072cf54d…b95c
0xe52b14…7230
5 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
3 conflicts on slot 0xa6e37efb84…caafc2
Audit this contract →
← previous block·next block →recent activity