← previous blocknext block →recent activity
Analyzing
Block #74,358,892
14 transactions · 12 stateful · 2026-05-13 16:45:01 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,358,892 · 14 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
1w02w110w011w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x0eac6378…36f4
0x34b655…2a6f
4 touches
1 conflict
0x615736c7…d953
0x065c9d…c394
4 touches
1 conflict
0x070a562a…8147
0x34b655…2a6f
4 touches
1 conflict
0x7fec573e…903f
0x065c9d…c394
3 touches
1 conflict
0x5e730412…680e
0x065c9d…c394
3 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
2 touches
0 conflicts
0x7d2b0df5…c45f
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity