← previous blocknext block →recent activity
Analyzing
Block #93,186,694
16 transactions · 14 stateful · 2026-08-04 23:02:24 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,186,694 · 16 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
1w02w04w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x840d3ab7…c8c4
0x34b655…2a6f
4 touches
1 conflict
0xe6e6f436…ddc0
0x34b655…2a6f
4 touches
1 conflict
0xd8bc53a3…c2fe
0x34b655…2a6f
4 touches
1 conflict
0x01dc29d8…bcd2
0x34b655…2a6f
2 touches
0 conflicts
0x1b9f1c76…23d5
0x34b655…2a6f
2 touches
0 conflicts
0x244fd0dc…ddcc
0x34b655…2a6f
2 touches
0 conflicts
0x4240f8ef…d73a
0x34b655…2a6f
2 touches
0 conflicts
0x53bda555…3810
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 0x840d3ab7c3…edc8c4
Audit this contract →
← previous block·next block →recent activity