← previous blocknext block →recent activity
Analyzing
Block #75,200,983
16 transactions · 13 stateful · 2026-05-17 14:29:56 UTC
Parallelism
56/100
Blocked
54%
Avg conflicts / tx
1.44
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #75,200,983 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w19w211w312w013w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x7170c140…36bc
0x34b655…2a6f
6 touches
3 conflicts
0x33018431…8f5d
0x188d58…ea8e
4 touches
1 conflict
0x18978822…2623
0x34b655…2a6f
4 touches
1 conflict
0x18b11fba…c92a
0x34b655…2a6f
4 touches
1 conflict
0x206f4379…e08a
0x34b655…2a6f
4 touches
1 conflict
0x297de2d5…7396
0x34b655…2a6f
4 touches
1 conflict
0x29cd05f5…390c
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity