← previous blocknext block →recent activity
Analyzing
Block #93,239,382
12 transactions · 12 stateful · 2026-08-05 03:27:17 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,239,382 · 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
1w04w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x216ffe66…1f94
0x34b655…2a6f
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0xc16edc63…e880
0xe52b14…7230
3 touches
1 conflict
0x12028e5c…112a
0x34b655…2a6f
2 touches
0 conflicts
0x15a76f59…f29c
0x34b655…2a6f
2 touches
0 conflicts
0x291ad0b4…69e9
0x34b655…2a6f
2 touches
0 conflicts
0x37d710c8…45c1
0x34b655…2a6f
2 touches
0 conflicts
0x704f5ff2…4c9a
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 0x216ffe6648…bf1f94
Audit this contract →
← previous block·next block →recent activity