← previous blocknext block →recent activity
Analyzing
Block #74,649,534
21 transactions · 16 stateful · 2026-05-15 01:07:26 UTC
Parallelism
81/100
Blocked
44%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,649,534 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w08w19w211w012w118w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0xadac4a86…c2bc
0x34b655…2a6f
6 touches
3 conflicts
0xc82b4db4…53d7
0x34b655…2a6f
6 touches
3 conflicts
0xe618b1fa…96ad
0x34b655…2a6f
4 touches
1 conflict
0x12fd91b6…cbe3
0x34b655…2a6f
4 touches
1 conflict
0x408e66bb…3d6b
0x34b655…2a6f
4 touches
1 conflict
0x4546ebad…b908
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity