← previous blocknext block →recent activity
Analyzing
Block #92,969,541
13 transactions · 13 stateful · 2026-08-04 04:48:48 UTC
Parallelism
77/100
Blocked
46%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,969,541 · 13 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
2w03w14w26w29w110w211w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x840d3ab7…c8c4
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xb9834665…e363
0x34b655…2a6f
4 touches
1 conflict
0xd8bc53a3…c2fe
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfcdb5918…2b49
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
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
1 conflict on slot 0x840d3ab7c3…edc8c4
Audit this contract →
← previous block·next block →recent activity