← previous blocknext block →recent activity
Analyzing
Block #74,787,896
12 transactions · 9 stateful · 2026-05-15 16:31:42 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,787,896 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xa02838a3…bc54
0x34b655…2a6f
4 touches
1 conflict
0x7edb13b3…8db1
0xd32edf…ff58
3 touches
1 conflict
0x229ea86d…b9cc
0x065c9d…c394
2 touches
0 conflicts
0x9b6962e4…7e41
0x065c9d…c394
2 touches
0 conflicts
0xc8f95b37…ef21
0x065c9d…c394
2 touches
0 conflicts
0xe354b091…9b0a
0x065c9d…c394
2 touches
0 conflicts
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity