← previous blocknext block →recent activity
Analyzing
Block #73,176,100
8 transactions · 6 stateful · 2026-05-08 05:16:07 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,176,100 · 8 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e66da19…66b6
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x25915cb4…b123
0x065c9d…c394
2 touches
0 conflicts
0x4521ac3a…f424
0x065c9d…c394
2 touches
0 conflicts
0x520a063f…66b5
0x065c9d…c394
2 touches
0 conflicts
0x8b19eb2e…3afd
0x065c9d…c394
2 touches
0 conflicts
0x95c011c5…21bb
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: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0x8e66da1932…c966b6
Audit this contract →
← previous block·next block →recent activity