← previous blocknext block →recent activity
Analyzing
Block #83,399,181
36 transactions · 18 stateful · 2026-06-24 14:05:47 UTC
Parallelism
94/100
Blocked
39%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,399,181 · 36 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
1w02w15w119w020w121w125w026w027w129w133w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0835adb5…ad83
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xb99958f6…ccf1
0x34b655…2a6f
4 touches
1 conflict
0xb99958f6…ccf0
0x34b655…2a6f
4 touches
1 conflict
0x8b305a3b…1c35
0x34b655…2a6f
4 touches
1 conflict
0x25f3833f…abbb
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0xff96dc9b…93d7
0x065c9d…c394
4 touches
1 conflict
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 0x0835adb553…f4ad83
Audit this contract →
← previous block·next block →recent activity