← previous blocknext block →recent activity
Analyzing
Block #73,200,103
19 transactions · 17 stateful · 2026-05-08 07:56:03 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,200,103 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w110w112w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x8e66da19…66b6
0x065c9d…c394
4 touches
1 conflict
0x251861eb…78fd
0x34b655…2a6f
4 touches
1 conflict
0x2a354a63…0515
0x065c9d…c394
4 touches
1 conflict
0xc7d5096a…5dc8
0x065c9d…c394
4 touches
1 conflict
0x87e04c0a…40aa
0x065c9d…c394
4 touches
1 conflict
0x1a4b4152…0a08
0x6ca43f…c331
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: MarginAccount
3 conflicts on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity