← previous blocknext block →recent activity
Analyzing
Block #74,331,043
30 transactions · 20 stateful · 2026-05-13 13:39:50 UTC
Parallelism
73/100
Blocked
50%
Avg conflicts / tx
0.93
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #74,331,043 · 30 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
3w05w18w29w317w018w124w225w326w427w528w629w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x4ac4a2c2…2707
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0xab3526…fa38
8 touches
6 conflicts
0x19dc684a…5f83
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x374426df…f445
0xc8689a…ee79
4 touches
1 conflict
0x01737532…9b12
0x34b655…2a6f
4 touches
1 conflict
0x189f735c…64fc
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity