← previous blocknext block →recent activity
Analyzing
Block #83,483,391
15 transactions · 12 stateful · 2026-06-24 23:28:10 UTC
Parallelism
87/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,483,391 · 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
2w08w19w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f068b13…fb19
0x34b655…2a6f
4 touches
1 conflict
0x8a381062…5ab8
0x065c9d…c394
4 touches
1 conflict
0xd8dd03ce…dc8d
0x2a68ba…90c5
4 touches
1 conflict
0x5d82c9b5…004c
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0003
0x5afd3e…7620
2 touches
0 conflicts
0x00000000…0004
0x5afd3e…7620
2 touches
0 conflicts
0x00000000…0005
0x5afd3e…7620
2 touches
0 conflicts
0xacc9cb0a…8f1e
0x5afd3e…7620
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 0x0f068b130e…d0fb19
Audit this contract →
← previous block·next block →recent activity