← previous blocknext block →recent activity
Analyzing
Block #74,183,973
7 transactions · 7 stateful · 2026-05-12 21:21:47 UTC
Parallelism
71/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,183,973 · 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x768cffcd…2648
0x34b655…2a6f
4 touches
1 conflict
0x8cc18498…ce7e
0x34b655…2a6f
4 touches
1 conflict
0xa8ddf3d3…ece4
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x1fdc185e…d080
0x065c9d…c394
2 touches
0 conflicts
0x408c8dd4…1b9b
0x065c9d…c394
2 touches
0 conflicts
0x9cdb0895…77f1
0x065c9d…c394
2 touches
0 conflicts
0xaf0edb55…9e7a
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 0x768cffcdb0…d12648
Audit this contract →
← previous block·next block →recent activity