← previous blocknext block →recent activity
Analyzing
Block #92,068,423
19 transactions · 18 stateful · 2026-08-01 01:15:04 UTC
Parallelism
84/100
Blocked
39%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,068,423 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w29w010w112w013w114w217w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4bc1abab…5874
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x00c43e68…2a3c
0x34b655…2a6f
5 touches
3 conflicts
0xb4382449…af3d
0x34b655…2a6f
4 touches
1 conflict
0xb6767190…e9b2
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x91855e…ac7e
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
3 conflicts on slot 0x4bc1abab4b…a45874
Audit this contract →
← previous block·next block →recent activity