← previous blocknext block →recent activity
Analyzing
Block #74,308,028
7 transactions · 7 stateful · 2026-05-13 11:06:48 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,308,028 · 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
0xeef70cb9…5de7
0xea1b8e…c5ec
4 touches
1 conflict
0x455b104f…3960
0xea1b8e…c5ec
4 touches
1 conflict
0xbc33a929…8b24
0xea1b8e…c5ec
4 touches
1 conflict
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0xd8eb2d31…2ac0
0xea1b8e…c5ec
4 touches
1 conflict
0x90a25e92…c4bd
0xaa3145…feec
2 touches
0 conflicts
0x4c4128a2…98e1
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: LeverUp: LeverUp
1 conflict on slot 0xeef70cb93b…ad5de7
Audit this contract →
← previous block·next block →recent activity