← previous blocknext block →recent activity
Analyzing
Block #73,693,856
19 transactions · 13 stateful · 2026-05-10 14:47:01 UTC
Parallelism
84/100
Blocked
31%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,693,856 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w010w012w113w014w116w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3e733ae4…4598
0x34b655…2a6f
4 touches
1 conflict
0xb245fe36…d765
0x34b655…2a6f
4 touches
1 conflict
0xd40bddc1…773c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0003
0x059114…ac3b
2 touches
0 conflicts
0x37b9bbd1…d9d2
0x059114…ac3b
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: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity