← previous blocknext block →recent activity
Analyzing
Block #73,418,563
12 transactions · 8 stateful · 2026-05-09 08:09:34 UTC
Parallelism
83/100
Blocked
13%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,418,563 · 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
6w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54f06ca4…a6e0
0x34b655…2a6f
4 touches
1 conflict
0x8240d70c…7c3b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x070a562a…8147
0x34b655…2a6f
4 touches
1 conflict
0x0eac6378…36f4
0x34b655…2a6f
4 touches
1 conflict
0x2a444366…fde4
0x34b655…2a6f
4 touches
1 conflict
0xf537eaa0…73c8
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: Perpl
1 conflict on slot 0x54f06ca444…eda6e0
Audit this contract →
← previous block·next block →recent activity