← previous blocknext block →recent activity
Analyzing
Block #83,628,019
15 transactions · 14 stateful · 2026-06-25 15:33:07 UTC
Parallelism
87/100
Blocked
21%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,628,019 · 15 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
2w03w19w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5d660d7…64e9
0xe1c8b7…3022
4 touches
1 conflict
0x4eb758b8…b13b
0x3bd359…433a
4 touches
1 conflict
0x67d846dd…358c
0x506682…7777
4 touches
1 conflict
0x7cf5136f…ba69
0x9f3832…4ae4
4 touches
1 conflict
0xf94c349c…d66d
0x9f3832…4ae4
4 touches
1 conflict
0xfce66a64…64e0
0x9f3832…4ae4
4 touches
1 conflict
0xfce66a64…64e1
0x9f3832…4ae4
4 touches
1 conflict
0xa164d951…1534
0xe1c8b7…3022
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: 0xe1c8b733…e33022
1 conflict on slot 0xc5d660d76e…4164e9
Audit this contract →
← previous block·next block →recent activity