← previous blocknext block →recent activity
Analyzing
Block #84,290,180
15 transactions · 14 stateful · 2026-06-28 17:07:00 UTC
Parallelism
87/100
Blocked
36%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,290,180 · 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
1w03w04w16w08w19w110w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0833f1ab…71e7
0x34b655…2a6f
4 touches
1 conflict
0x12dd43c9…22d9
0x34b655…2a6f
4 touches
1 conflict
0x18978822…2623
0x34b655…2a6f
4 touches
1 conflict
0x216b4ce7…2b99
0x34b655…2a6f
4 touches
1 conflict
0x2c5bae60…bc2e
0x34b655…2a6f
4 touches
1 conflict
0x4bb3539b…b005
0x34b655…2a6f
4 touches
1 conflict
0x4bdcc5ee…7e90
0x34b655…2a6f
4 touches
1 conflict
0x4d93a3e4…5169
0x34b655…2a6f
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 0x0833f1ab37…fd71e7
Audit this contract →
← previous block·next block →recent activity