← previous blocknext block →recent activity
Analyzing
Block #93,567,938
16 transactions · 13 stateful · 2026-08-06 06:59:06 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,567,938 · 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
7w09w010w111w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6bb22c3…4a4f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xc73549e8…2001
0x34b655…2a6f
4 touches
1 conflict
0x7a2c83a3…a29a
0x34b655…2a6f
4 touches
1 conflict
0x1cfbfb90…7f50
0x851145…3f07
3 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
1 conflict on slot 0xb6bb22c3ba…d64a4f
Audit this contract →
← previous block·next block →recent activity