← previous blocknext block →recent activity
Analyzing
Block #83,642,824
14 transactions · 13 stateful · 2026-06-25 17:12:02 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,642,824 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w18w112w013w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7534f53d…6ed4
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xaa7ee7…f0e4
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x06946ed5…62a0
0x34b655…2a6f
2 touches
0 conflicts
0x1e9bc0f3…8d42
0x34b655…2a6f
2 touches
0 conflicts
0x4137e932…cf41
0x34b655…2a6f
2 touches
0 conflicts
0x54daebc3…98e1
0x34b655…2a6f
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
3 conflicts on slot 0x7534f53d7a…5a6ed4
Audit this contract →
← previous block·next block →recent activity