← previous blocknext block →recent activity
Analyzing
Block #74,762,374
19 transactions · 18 stateful · 2026-05-15 13:40:58 UTC
Parallelism
89/100
Blocked
17%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,762,374 · 19 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
4w05w17w08w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x1f7def57…a428
0x065c9d…c394
2 touches
0 conflicts
0x2cf5fea4…6f12
0x065c9d…c394
2 touches
0 conflicts
0xb196d2f2…15cb
0x065c9d…c394
2 touches
0 conflicts
0xb6e2eda5…f1b9
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 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity