← previous blocknext block →recent activity
Analyzing
Block #93,593,949
12 transactions · 12 stateful · 2026-08-06 09:09:51 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,593,949 · 12 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
5w06w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x666f54f8…873c
0x34b655…2a6f
4 touches
1 conflict
0x4f93e8cf…8eec
0x34b655…2a6f
4 touches
1 conflict
0x6d74089c…c836
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x14eb2f47…8a2e
0x34b655…2a6f
2 touches
0 conflicts
0x68fbcfc9…64b7
0x34b655…2a6f
2 touches
0 conflicts
0x6d1b72ee…6b77
0x34b655…2a6f
2 touches
0 conflicts
0x6d1b72ee…6b78
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 0x666f54f891…32873c
Audit this contract →
← previous block·next block →recent activity