← previous blocknext block →recent activity
Analyzing
Block #74,246,181
7 transactions · 5 stateful · 2026-05-13 04:15:30 UTC
Parallelism
71/100
Blocked
20%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,246,181 · 7 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x5e3bfff1…7e91
0x34b655…2a6f
4 touches
1 conflict
0xdf717eac…a7e8
0x34b655…2a6f
4 touches
1 conflict
0xb654bd89…a83b
0x34b655…2a6f
4 touches
1 conflict
0xaa3b4402…74e6
0x34b655…2a6f
3 touches
1 conflict
0x51087f5a…61f7
0x34b655…2a6f
2 touches
0 conflicts
0x56abd81e…9808
0x34b655…2a6f
2 touches
0 conflicts
0x59a54ff4…d21b
0x34b655…2a6f
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity