← previous blocknext block →recent activity
Analyzing
Block #71,647,681
18 transactions · 16 stateful · 2026-05-01 03:30:03 UTC
Parallelism
56/100
Blocked
56%
Avg conflicts / tx
1.67
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #71,647,681 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w16w110w011w112w213w314w415w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x1c913164…5c2e
0x34b655…2a6f
6 touches
3 conflicts
0x37674bd8…8f35
0x34b655…2a6f
4 touches
1 conflict
0x37cfaf01…4a46
0x34b655…2a6f
4 touches
1 conflict
0x37d49489…9309
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x55b6a001…1e7a
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity