← previous blocknext block →recent activity
Analyzing
Block #74,771,391
18 transactions · 11 stateful · 2026-05-15 14:41:23 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,771,391 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w115w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0efc210e…70ab
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfd298f7a…3682
0xd32edf…ff58
3 touches
1 conflict
0x1f7def57…a428
0x065c9d…c394
2 touches
0 conflicts
0x25fc3ff1…3254
0x065c9d…c394
2 touches
0 conflicts
0x348fda08…7e96
0x065c9d…c394
2 touches
0 conflicts
0x77ad85bf…a1e9
0x065c9d…c394
2 touches
0 conflicts
0x85736409…f76b
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 0x0efc210ee8…0e70ab
Audit this contract →
← previous block·next block →recent activity