← previous blocknext block →recent activity
Analyzing
Block #83,667,418
16 transactions · 15 stateful · 2026-06-25 19:56:03 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,667,418 · 16 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
1w02w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xad88d4fd…bb7f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x18904470…0ef9
0x34b655…2a6f
4 touches
1 conflict
0x344bc09a…942f
0x34b655…2a6f
4 touches
1 conflict
0x211ca66e…faaa
0x065c9d…c394
2 touches
0 conflicts
0xdc87b262…7b42
0x065c9d…c394
2 touches
0 conflicts
0x40970e69…da50
0x69df8a…6292
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 0xad88d4fd59…78bb7f
Audit this contract →
← previous block·next block →recent activity