← previous blocknext block →recent activity
Analyzing
Block #74,307,021
12 transactions · 11 stateful · 2026-05-13 11:00:05 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,307,021 · 12 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
2w010w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7cee1be1…e770
0x34b655…2a6f
4 touches
1 conflict
0xbb1747e2…f78b
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xbd2af710…34d9
0x1efe02…37d6
2 touches
0 conflicts
0x1728ed63…499c
0xea1b8e…c5ec
2 touches
0 conflicts
0x455b104f…3960
0xea1b8e…c5ec
2 touches
0 conflicts
0x6a35f85c…0190
0xea1b8e…c5ec
2 touches
0 conflicts
0x9c8d6dd6…d619
0xea1b8e…c5ec
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 0x7cee1be1f4…b4e770
Audit this contract →
← previous block·next block →recent activity