← previous blocknext block →recent activity
Analyzing
Block #93,343,993
19 transactions · 16 stateful · 2026-08-05 12:13:14 UTC
Parallelism
89/100
Blocked
6%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,343,993 · 19 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
3w08w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02fdb0e0…b418
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x840d3ab7…c8c4
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x0de8f3e9…a865
0x34b655…2a6f
2 touches
0 conflicts
0x2f358e74…1022
0x34b655…2a6f
2 touches
0 conflicts
0x78d18f75…b521
0x34b655…2a6f
2 touches
0 conflicts
0x9e599b87…c270
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 0x02fdb0e064…efb418
Audit this contract →
← previous block·next block →recent activity