← previous blocknext block →recent activity
Analyzing
Block #74,786,814
20 transactions · 13 stateful · 2026-05-15 16:24:27 UTC
Parallelism
80/100
Blocked
46%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,786,814 · 20 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
6w09w113w215w316w017w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x2c3877f4…1f8f
0xd32edf…ff58
7 touches
6 conflicts
0x84fb2a36…db89
0x34b655…2a6f
6 touches
3 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
6 touches
3 conflicts
0x8c49c85c…ee96
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x1952c598…df64
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity