← previous blocknext block →recent activity
Analyzing
Block #93,268,459
16 transactions · 16 stateful · 2026-08-05 05:53:29 UTC
Parallelism
56/100
Blocked
44%
Avg conflicts / tx
1.31
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,268,459 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w15w26w38w410w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x033cf007…136d
0x34b655…2a6f
12 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
12 touches
15 conflicts
0xf3d10975…0d07
0x34b655…2a6f
10 touches
10 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xf1b9adf0…fa78
0x34b655…2a6f
5 touches
3 conflicts
0x4bc1abab…5874
0x34b655…2a6f
5 touches
3 conflicts
0x5cc78005…4877
0x34b655…2a6f
4 touches
1 conflict
0x39921786…0b17
0x34b655…2a6f
4 touches
1 conflict
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
15 conflicts on slot 0x033cf007c8…d2136d
Audit this contract →
← previous block·next block →recent activity