← previous blocknext block →recent activity
Analyzing
Block #75,937,519
16 transactions · 12 stateful · 2026-05-21 00:33:45 UTC
Parallelism
88/100
Blocked
25%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,937,519 · 16 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
1w02w16w07w19w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6527b0cd…3c03
0x34b655…2a6f
4 touches
1 conflict
0x676f9f01…a8ac
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0xc7d2d9f3…378b
0xd32edf…ff58
3 touches
1 conflict
0x2284c7d6…a9c7
0x065c9d…c394
2 touches
0 conflicts
0x443a3e47…f4a4
0x065c9d…c394
2 touches
0 conflicts
0x736444f4…1fa2
0x065c9d…c394
2 touches
0 conflicts
0xaee39043…1370
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 0x6527b0cd80…2c3c03
Audit this contract →
← previous block·next block →recent activity