← previous blocknext block →recent activity
Analyzing
Block #74,190,456
11 transactions · 10 stateful · 2026-05-12 22:04:51 UTC
Parallelism
64/100
Blocked
30%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,190,456 · 11 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
7w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x768cffcd…2648
0x34b655…2a6f
6 touches
3 conflicts
0x41d3bfa5…523e
0x34b655…2a6f
6 touches
3 conflicts
0xfd784183…67bb
0x34b655…2a6f
4 touches
1 conflict
0x1bb36615…bef1
0x34b655…2a6f
4 touches
1 conflict
0xba3f84a5…4c26
0x34b655…2a6f
4 touches
1 conflict
0xe5e7089a…fb91
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